← All tasks
javambechler/marshalsec #15Repaired task

Missing dependency javax.activation

envgap__mbechler__marshalsec-15

01 / FAILURE SIGNATURE

Captured in a clean container

[ERROR] COMPILATION ERROR :

02 / ENVIRONMENT RECIPE

Base commit
6aa34343a715e53c94f2e65aaaeb243f83fb5d8c
Manifest
pom.xml
Reproduce
mvn -B -q -Dgpg.skip -Dmaven.javadoc.skip=true -Dcheckstyle.skip -DskipTests package
Run under trace
mvn -B -q -Dgpg.skip -Dmaven.javadoc.skip=true -Dcheckstyle.skip -DskipTests package
Reference environment fix used for admission
diff --git a/pom.xml b/pom.xml
index bbb9ef6..5d25e0b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -15,6 +15,12 @@
 	<dependencies>
 
 		<!-- Util -->
+		<dependency>
+			<groupId>com.sun.activation</groupId>
+			<artifactId>javax.activation</artifactId>
+			<version>1.2.0</version>
+		</dependency>
+
 		<dependency>
 			<groupId>org.javassist</groupId>
 			<artifactId>javassist</artifactId>

03 / ORIGINAL ISSUE TEXT

mbechler/marshalsec #15 · read the original issue
Hello,



I get the following error when compiling on Kali:



```

[ERROR] /opt/marshalsec/src/main/java/marshalsec/gadgets/JDKUtil.java:[52,24] package javax.activation does not exist

```



Adding the following block to the `<dependencies>` section of the pom.xml file does the trick:



```

<dependency>

    <groupId>javax.activation</groupId>

    <artifactId>activation</artifactId>

    <version>1.1.1</version>

</dependency>

```



Cheers!
Continue on GitHub ↗

04 / LABELS

Labels checked by running the task · needs human review

No supported category has been assigned.

Label rules and the text that matched
[]

Mined from a merged pull request linked to the issue whose changed files are all environment files.

The base commit is the pull request's base, not the dated default-branch commit; the registry is pinned to the merge date so the pull request's own pins resolve.

Default commands from envgap default-recipe synthesizer v1; gold_files are the pull request's environment diff.

Preparation uses current registries. Historical package availability is not enforced here; execution metadata records this limitation separately from the oracle's date-bounding policy.