Revert "prepare release"

This reverts commit 814bcf1.

Author: niesfisch

.github/workflows/release.yml

@@ -12,7 +12,6 @@ If you work in a legacy app and ask things like "Can we remove this?" or "Is thi
 - [Recommended Local Workflow: ELK](#recommended-local-workflow-elk)
 - [Project Status](#project-status)
 - [Java Version](#java-version)
-- [Download a Release Jar](#download-a-release-jar)
 - [Build](#build)
 - [Configure](#configure)
 - [Run an Application with JCT](#run-an-application-with-jct)
@@ -52,13 +51,11 @@ This is especially useful before deleting legacy code, splitting modules, or tig
 
 If you just want first results quickly:
 
-1. Download the release jar or build JCT locally
+1. Build JCT
 2. Start your app with `-javaagent` and a config
 3. Inspect generated events (file output or ELK stack)
 
-Fastest path: download the fat jar from GitHub Releases and use it directly.
-
-Manual build commands:
+Minimum commands:
 
 ```bash
 mvn clean package
@@ -104,31 +101,10 @@ This project targets Java 8 bytecode and is currently focused on practical runti
 JCT is compiled against Java 8 (`-source 8 -target 8`) and intentionally uses no APIs beyond that level.
 This is a deliberate choice — the primary target is legacy and monolithic systems that are often stuck on older JVMs.
 
-It runs fine on newer JVMs (11, 17, 21, ...) without any changes.
-
-## Download a Release Jar
-
-If you do not want to build JCT locally, download the prebuilt agent jar here:
-
-- [GitHub Releases](https://github.com/niesfisch/java-code-tracer/releases)
-- [Release workflow runs and downloadable artifacts](https://github.com/niesfisch/java-code-tracer/actions/workflows/release.yml)
-
-Use this file as your Java agent:
-
-- `java-code-tracer-<version>-jar-with-dependencies.jar`
-
-The release workflow publishes the jar in two places:
-
-- as a GitHub Release asset for tagged releases
-- as a workflow artifact for each `Release Jar` workflow run
-
-For maintainers: pushing a tag like `v1.0.0` starts the release workflow automatically.
-You can also trigger `Release Jar` manually in GitHub Actions and provide a tag name.
+It runs fine on newer JVMs (11, 17, 21, …) without any changes.
 
 ## Build
 
-Build locally with Maven if you prefer or if you want to modify the project:
-
 ```bash
 mvn clean package
 ```
@@ -137,8 +113,6 @@ The distributable agent jar is created at:
 
 - `target/java-code-tracer-1.0-SNAPSHOT-jar-with-dependencies.jar`
 
-That is the jar you should use with `-javaagent`.
-
 ## Configure
 
 Create a local config file:
@@ -327,3 +301,4 @@ Use the following IntelliJ Run/Debug VM options example when attaching JCT as a
 ## License
 
 [MIT](LICENSE.txt)
+

README.md

@@ -12,7 +12,8 @@
     <properties>
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
         <java.version>8</java.version>
-        <maven.compiler.release>${java.version}</maven.compiler.release>
+        <maven.compiler.source>${java.version}</maven.compiler.source>
+        <maven.compiler.target>${java.version}</maven.compiler.target>
         <maven.surefire.plugin.version>3.2.5</maven.surefire.plugin.version>
         <maven.compiler.plugin.version>3.13.0</maven.compiler.plugin.version>
         <maven.assembly.plugin.version>3.7.1</maven.assembly.plugin.version>
@@ -31,7 +32,22 @@
         </license>
     </licenses>
 
+    <repositories>
+        <repository>
+            <id>Sonatype-public</id>
+            <name>SnakeYAML repository</name>
+            <url>http://oss.sonatype.org/content/groups/public/</url>
+        </repository>
+    </repositories>
+
     <dependencies>
+        <dependency>
+            <groupId>com.sun</groupId>
+            <artifactId>tools</artifactId>
+            <version>1.6.0</version>
+            <scope>system</scope>
+            <systemPath>${java.home}/../lib/tools.jar</systemPath>
+        </dependency>
         <dependency>
             <groupId>org.yaml</groupId>
             <artifactId>snakeyaml</artifactId>
@@ -81,7 +97,8 @@
                 <artifactId>maven-compiler-plugin</artifactId>
                 <version>${maven.compiler.plugin.version}</version>
                 <configuration>
-                    <release>${maven.compiler.release}</release>
+                    <source>${maven.compiler.source}</source>
+                    <target>${maven.compiler.target}</target>
                 </configuration>
             </plugin>