I know that the new release flag is supposed to be better in keeping runtime
API versions separate, do we know it works?
It was a risk in the past to not use the target Java version (or at least the
boot classpath), do you think it’s needed? As far as I know we don’t have
Multi-Release magic in
Just curious if we want to send 3.9 out? Build on java 11 targeting java 8?
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
+1 (non-binding)
Signatures and SHA512 hashes verified; RELEASE-NOTES.txt looks good.
Build, test and site generation OK in my env:
$ mvn -v
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T15:39:06-04:00)
Maven home: ...
Java version: 1.8.0_144, vendor: Oracle Corporation
