← Back to team overview

openjdk team mailing list archive

Bug#911925: Latest OpenJDK breaks various builds

 

severity 911925 grave
thanks

Grave because this causes odd errors in various Java compilation tasks, and possibly in some Java applications, to make sure this version doesn't easily enter testing.


Apparently this upload causes various build problems in particular with Maven (surefire) but also ant.

Here is an ant error when trying to "ant compile" UMLgraph: https://github.com/dspinellis/UMLGraph
---

compile:
    [javac] Compiling 20 source files to /home/erich/workspace/UMLGraph/build     [javac] /home/erich/workspace/UMLGraph/src/main/java/org/umlgraph/doclet/ClassGraph.java:323: error: cannot access ClassDoc     [javac]         optionProvider.getOptionsFor(c instanceof ClassDoc ? (ClassDoc) c : c.containingClass()) //
    [javac]                       ^
    [javac]   class file for ClassDoc not found

---

Now tools.jar is on the classpath, it seems to be in the package (but possibly the binary is broken?)

With maven, I get a different failure:

---

[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ umlgraph ---
[INFO] Surefire report directory: /home/erich/workspace/UMLGraph/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Error: Could not find or load main class org.apache.maven.surefire.booter.ForkedBooter

[...]

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project umlgraph: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ? -> [Help 1]

---

The same surefire problem was also reported here: https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class/53016532#53016532

On other systems, the package builds fine, including on Travis CI.


It seems this only affects certain (system?) class loader scenarios - surefire adds a jar, and the ant build needs the tools.jar.

My guess is that the backport of the security fixes didn't completely work...

Regards,
Erich