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 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 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.

@loke @martin Wow, that's rough. Is ABCL essentially unmaintained these days, or are later Java VMs hostile to one of it's implementation techniques?

@tfb @martin The latter. As far as I understand, the way they generate bytecodes and compile it on the fly when defining a function can't be used anymore.

Sign in to participate in the conversation
Functional Café

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!