We currently ship 2.4 (despite the license file which claims 2.3). 2.6 is marked on their website as the latest "legacy" release, and 3.1 is recommended.
For bdf59cfe5ce5 I really needed a Pair<T,U> class. I do not really want to stuff this generic language utility into org.openide.util when org.apache.commons.lang3.tuple.ImmutablePair (@since 3.0) already does what I want.
2.x and 3.x use different package names; probably they could both be bundled?
> 2.x and 3.x use different package names; probably they could both be bundled?
org.apache.commons.lang 2.4 is shipped with mylyn which wouldn't work with >= 3.0 so no motivation in issue tracking to upgrade.
seems to be possible to bundle both packages, but the owner of #bdf59cfe5ce5 should decide
I'm slightly confused here. bdf59cfe5ce5 doesn't require currently commons-lang3. But it could be rewritten to use it?
is this issue about creating new module org.apache.commons.lang3 ? with a different codenamebase from the current org.apache.commons.lang module?
moving to enhancement until convinced otherwise, I'm not seeing a defect here.