On 23 May 2017 at 16:07, sebb <seb...@gmail.com> wrote: > Huh? > > The whole point of changing the package name and Maven coords is to > allow mutually incompatible jars to coexist peacefully on a single > classpath.
All you are doing in replacing one kind of jar hell with another. Removing these methods means that a project that wants to use them has to use the older version. But if another dependency needs a later version you have hell. However, if one dependency uses lang3 Pair and another uses lang4 Pair, you can't make the API call without a messy conversion. Yes, the code compiles and both can be on the classpath, but it is a pain to use, just a different kind of hell. What I'm saying is that I'm unconvinced any use of the lang4 package is a particularly good idea. Having 2 versions of lang out there has avoided some problems but created others. Add lang4 package IMO creates as many issues as it solves. Anyway, its not really my choice. If the [lang] maintainers want absolute backwards compatibility, so be it. I can prepare a module-info based on an optional dependency. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
