Hi. > [...] > > So there are at least two options: > > 1. Release using JDK 9
+1 > 2. Update the examples project to use source 11 for the Java modules code and > release using a non-oracle JDK 11 > > Note that updating to use source 11 will break the Jenkins build which uses > JDK 9 to run a full build including the -P commons-rng-examples profile. This > could be ignored, updated to JDK 11 or dropped in favour of adding an > appropriate JDK 11 run using Travis. > > Another option is to somehow get around the javadoc issue with modules and > unnamed modules. Let's not delay because of side issues. :-) Hopefully, this will be fixed in a future JDK version, or when we upgrade the target of all modules. Best, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
