I'm not amused by these days.

maven won't deploy with java-11 because
> javadoc: error - The code being documented uses modules but the packages defined in docs.oracle.com/javase/7/docs/ are in the unnamed module.

and it won't deploy with java-8, because
> Execution default-test of goal XXX failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?

java-7 can't be installed because of dependency issues

and that's again when the hacking starts... 🤦‍

@martin To me, this looks like a hint that you should upgrade your dependencies, e.g. Java SE too.
I'm upgrading our project to Java 11 too atm and at least I can build & run it again by now. 🙈


@Aarkon well java 11 is the current version, isn't it? but my issue is actually a bug in openjdk 11+ bugs.openjdk.java.net/browse/J

Their workaround is to pollute the pom to use java-8 for javadoc (and java-11 for the rest). But... no. :angry_trump:

My workaround is to replace the javadoc binary in java-11 with a link to the binary in java-8:

/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc -> /usr/lib/jvm/java-8-openjdk-amd64/bin/javado

and wait until their official fix drips down to my setup...

@martin Oh, too bad! But your "fix" looks looks nice, and a lot cleaner than mixing project configuration with treatment of issues in external binaries!

Sign in to participate in the conversation

mstdn.binfalse.de is one server in the network