On 23 May 2017 at 11:05, Stephen Colebourne <scolebou...@joda.org> wrote: > On 22 May 2017 at 00:56, Benedikt Ritter <brit...@apache.org> wrote: >> I think the time has come to start thinking about Lang 4.0. > > As I outlined in another thread, Lang 3.5 uses PropertyChangeListener, > which in module terms pulls in the whole of Swing and AWT. For a > library like [lang] that is a bad thing and should really be fixed. > > Fixing it properly requires a major release, which implies that Lang > 4.0 is still Java 1.7 and should use the `org.apache.commons.lang3` > package name.
I think that depends on whether the API is backwards-compatible or not. If it *is* backwards-compatible, then do we need a major release? If *not*, then 4.0 needs a new package. Why? Suppose code A depends on a LANG 3 method not present in 4 and code B depends on some new feature in LANG 4 It's not possible to use A and B together on the same classpath. In which case 4.0 must use a new package and Maven coordinates. > Yes, the versioning a bit of a mess, but you are where you are. > > More broadly, it needs to be established if a lang release for Java 8 > is needed? What would it enable? Would a new commons project be a > better place for them (ie. a new [core] or [eight] project)? > > Stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
