Le 9/10/2017 à 18:32, Gary Gregory a écrit :
> 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?
Good idea, I added some examples to the public methods.
Emmanuel Bourg
---
I've been using maven-javadoc-plugin 3.0.0.M1 on other projects and that
works.
Gary
On Mon, Oct 9, 2017 at 2:15 PM, Emmanuel Bourg wrote:
> Thank you for the trace. This error is actually triggered by
> maven-javadoc-plugin 2.10.4 which depends on commons-lang 2.5. It should
> be fixed in the
Le 9/10/2017 à 22:15, Emmanuel Bourg a écrit :
> ...by maven-javadoc-plugin 2.10.4 which depends on commons-lang 2.5.
Actually it depends on commons-lang 2.4, not 2.5.
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@com
Thank you for the trace. This error is actually triggered by
maven-javadoc-plugin 2.10.4 which depends on commons-lang 2.5. It should
be fixed in the version 3.0.0. maven-site-plugin 3.6 already uses
commons-lang3.
Emmanuel Bourg
--
The error also shows commons-lang-2.4 in use, not 2.6.
Gary
On Mon, Oct 9, 2017 at 2:06 PM, Gary Gregory wrote:
> Note that the Doxia site tools plugin has just been updated to use
> [lang3], so a new release of the Maven Site plugin should pick it up soon.
>
> Gary
>
> On Mon, Oct 9, 2017 at 1
Note that the Doxia site tools plugin has just been updated to use [lang3],
so a new release of the Maven Site plugin should pick it up soon.
Gary
On Mon, Oct 9, 2017 at 1:54 PM, Gary Gregory wrote:
>
>
> On Mon, Oct 9, 2017 at 1:28 PM, Emmanuel Bourg wrote:
>
>> Le 9/10/2017 à 18:29, Gary Gre
On Mon, Oct 9, 2017 at 1:28 PM, Emmanuel Bourg wrote:
> Le 9/10/2017 à 18:29, Gary Gregory a écrit :
> > 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
Le 9/10/2017 à 18:29, Gary Gregory a écrit :
> 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 blow
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
wrote:
> One way to test isJavaVersionAtLeast for sure would be to ins
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, 2
Looks good AFAICT
Stephen
On 9 October 2017 at 14:39, Emmanuel Bourg 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
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
> Am 29.09.2017 um 10:08 schrieb Emmanuel Bourg :
>
> Hi all,
>
> 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.isJavaVers
I think we should keep the changes to a minimum.
Gary
On Sep 29, 2017 02:08, "Emmanuel Bourg" wrote:
> Hi all,
>
> 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
Hi all,
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 Except
15 matches
Mail list logo