Can you please update the Javadocs on the various methods that show Java versions with examples up to Java 9 to make it clear that the Java 9 use case is handled?
Thank you, Gary On Mon, Oct 9, 2017 at 10:29 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > One way to test isJavaVersionAtLeast for sure would be to install lang > 2.7 locally and, for example, take the current [configuration] 2.2 RC and > update the POM to use [lang] 2.7 with the Maven Site plugin. The Maven Site > plugin 3.6 currently blows up on isJavaVersionAtLeast. > > Gary > > On Mon, Oct 9, 2017 at 7:39 AM, Emmanuel Bourg <ebo...@apache.org> wrote: > >> Le 29/09/2017 à 10:08, Emmanuel Bourg a écrit : >> >> > I'd like to prepare a new release of Commons Lang 2 that addresses the >> > Java 9 compatibility. I have two items in mind for this update, the >> > automatic module name in the manifest of course, but also the >> > SystemUtils.isJavaVersionAtLeast() method that is broken with Java 9 >> and >> > throws an Exception. This would be a minimal update branched off the >> > latest 2.6 release. >> >> I prepared the changes on GitHub: >> >> https://github.com/ebourg/commons-lang/tree/LANG_2_X >> >> I started from the 2.x branch since it contained a few fixes worth >> keeping. The exception I was seeing with SystemUtils >> isJavaVersionAtLeast() was actually fixed in 2.6, so I just added the >> automatic module name to the manifest (I used org.apache.commons.lang as >> name assuming commons-lang3 would use org.apache.commons.lang3). I >> updated the release notes but not the site since it's published from the >> master branch. >> >> Please review, I intend to merge the changes and roll the release next >> week. >> >> Emmanuel Bourg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> >
