Hi Dave, Dave Brosius wrote:
> Hi Folks, > > > I'd like to see all of our common components uptake the 'latest' > versions of other commons components, to encourage their adoption. For > instance, commons-beanutils still uses commons-collections 3, and so > when i want to use commons-collections4 myself, i now have to have both > in the classpath. While there are no conflicts, it's just messy. People > auto-import the wrong version of collections classes into our code base, > for instance. If we could get updates to at least the right (major) > version of jars that would be great. unfortunately this is not always possible without creating a new major version (i.e. new package name) for the component itself. It will work if the types from the dependency are used internally only. E.g. commons-configuration 1.x used an exception in its API that was from commons-lang 2.x, therefore you could not upgrade to latest commons-lang without breaking common-configuration's API too. Cheers, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
