download-jdk VS moditect

There are plenty of vendors providing builds of OpenJDK free to use in production including Oracle themselves. Oracle's build of OpenJDK that is free to use in production is found here: https://jdk.java.net.

Java can also be found in OpenJDK. Download your version, extract it (usually, the default directory is /usr/lib/jvm), and point the java program.

As someone else has mentioned, Oracle JDK still has limitations when used in commercial applications. However, there are lots of JDKs that are free to use for anything you want to do with it. jdk.java.net is where I used to get mine from. If you want an installer adoptium.net is also great (that's the JDK provided by the Eclipse foundation).

Java.com is the website for the product Java. Oracle owns java as mentioned in 1 so it makes sense they would have java-related things on their website. jdk.java.net is the domain for the Oracle OpenJDK

This, the oracle JDK from oracle.com.. Not the Oracle build of the JDK from http://jdk.java.net/ which has always been free.

https://jdk.java.net/ is probably the most standard as those are the build from openjdk itself. The eclipse temurn is a different Openjdk build by a different organization.

OpenJDK is an open-source project. The key word there is 'source'. OpenJDK does not provide binary distributions. Yes, there is one available from jdk.java.net but that is the Oracle OpenJDK JDK.

And then you have to use moditect to generate a module-info.java and this is again because the annotation processor will pick up the provides Processor with YourAnnotationProcessor.

Maybe you've somehow missed https://maven.apache.org/plugins/maven-jlink-plugin/ https://github.com/moditect/moditect https://github.com/beryx/badass-jlink-plugin https://github.com/sormuras/testing-in-the-modular-world

Yes, you are right. jlink does not work with automatic modules. But using that plugin https://github.com/moditect/moditect you can easily transform almost any java library into a named module. It is a shame there are libraries under development, that have not been adapted to the java modular system.

FWIW, I've had a lot more issues with reflective access when using GraalVM. Reflection is mainly a problem with modules if you forget to 'open' your modules which is easy to fix in many cases. There's also moditect if the library author still doesn't want to learn how to include a module-info in the legacy compatible jar.

Or apply the https://github.com/moditect/moditect plugin and keep the build in JDK8. Let the plugin create the module descriptors without configuring JDK toolchains.

You can use the https://github.com/moditect/moditect maven plugin to add the module-info to the third-party jars

The next solution, which is the one I'm writing about. Is to modularize foo's jar, this is easily accomplished using the moditect plugin. But it can be tricky since I don't have, nor do I need, bar, and I prefer doing most of the work in build time and not manually.

It's possible to add this information during one's build even though the procedure is error-prone and boring. The description on how to achieve this deserves a post on its own. For more information, please check this Oracle magazine article. Suffice to say here that it makes heavy use of the Moditect Maven plugin.