I'm not amused by #openjdk these days.
maven won't deploy with java-11 because
> javadoc: error - The code being documented uses modules but the packages defined in http://docs.oracle.com/javase/7/docs/api/ 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. 🙈
Their workaround is to pollute the pom to use java-8 for javadoc (and java-11 for the rest). But... no.
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!
@martin Java 11 is a bit of a mess. Up until 8 they preserved Java backwards compatibility so that (almost) all code would run unchanged. Now, it's a different story, and a lot of complex software can't run anymore.
In particular, ABCL can't run on anything newer than 8, and probably will never be able to.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!