Apache commons lang and lang3

[Zac Jacobson]

The package name for the module org.apache.commons commons-lang is different between 2.X and 3.X - it's supposed to be possible for both packages to be on the classpath at the same time

from http://commons.apache.org/proper/commons-lang/

Note that Lang 3.0 (and subsequent versions) use a different package (org.apache.commons.lang3) than the previous versions (org.apache.commons.lang), allowing it to be used at the same time as an earlier version.

In Maven, the artifact ID for 3.x is "commons-lang3" - is it possible to mirror that approach in ivyroundup?

[Archie Cobbs]

Good idea.

Committed in r2708.

-Archie

--
You received this message because you are subscribed to the Google Groups "ivyroundup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ivyroundup+...@googlegroups.com.
To post to this group, send email to ivyro...@googlegroups.com.
Visit this group at http://groups.google.com/group/ivyroundup?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Archie L. Cobbs

[Zac Jacobson]

Awesome, thanks!

[Zac Jacobson]

Is it worth putting a patch together to update all the commons-lang dependencies to commons-lang3, or would that cause more problems than it solves?

[Zac Jacobson]

Not ALL, obviously. But the ones that depend on [3.0,)

[Archie Cobbs]

Well, you're right to point out that it's an issue we have to tackle either now or later.

Might as well be now... thanks for volunteering :)

-Archie

On Thu, Jun 13, 2013 at 10:29 PM, Zac Jacobson <pie...@gmail.com> wrote:

Is it worth putting a patch together to update all the commons-lang dependencies to commons-lang3, or would that cause more problems than it solves?

--
You received this message because you are subscribed to the Google Groups "ivyroundup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ivyroundup+...@googlegroups.com.
To post to this group, send email to ivyro...@googlegroups.com.

Visit this group at http://groups.google.com/group/ivyroundup.

For more options, visit https://groups.google.com/groups/opt_out.

--
Archie L. Cobbs

[Zac Jacobson]

Do you prefer a patch, or a shell/python script to recursively step through things and make the changes?

Should all versions be updated, or just latest revision?

Afterwards, would people have to wipe out their /.iv2/cache directories to account for changing checksums for ivy.xml files? Is that okay?

[Archie Cobbs]

On Fri, Jun 14, 2013 at 3:29 PM, Zac Jacobson <pie...@gmail.com> wrote:

Do you prefer a patch, or a shell/python script to recursively step through things and make the changes?

Just a patch is fine.. this will be a one-time thing.
 

Should all versions be updated, or just latest revision?

The conservative thing to do is update any <dependency> to commons-lang that has a lower revision bound of 3.x or higher.

Afterwards, would people have to wipe out their /.iv2/cache directories to account for changing checksums for ivy.xml files? Is that okay?

I don't think that will be necessary. This change will be backward-compatible in the near term so it doesn't matter if people are still caching the old ivy.xml versions. The JAR you end up with will be the same.

-Archie

--
Archie L. Cobbs

[Zac Jacobson]

I was surprised: there didn't seem to be many affected. patch attached.

[Archie Cobbs]

Thanks, patch applied in r2722.

-Archie

--

You received this message because you are subscribed to the Google Groups "ivyroundup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ivyroundup+...@googlegroups.com.
To post to this group, send email to ivyro...@googlegroups.com.
Visit this group at http://groups.google.com/group/ivyroundup.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Archie L. Cobbs