2015-02-19 16:14 GMT+01:00 Ben McCann <b...@benmccann.com>: > Why do you say users would have to rename all their import statements? Is > there a patch pending that we're consider which would change the package > name? I don't think there'd be any changes that be hard for end users to > deal with that I'm aware of. >
Changing the major version number for a commons component always implies changing maven coords and the package name. We do this, so that several versions of the same commons component can be in the same classpath. Benedikt > > On Thu, Feb 19, 2015 at 7:07 AM, Benedikt Ritter <brit...@apache.org> > wrote: > > > 2015-02-19 16:06 GMT+01:00 Emmanuel Bourg <ebo...@apache.org>: > > > > > Le 19/02/2015 15:17, Ben McCann a écrit : > > > > Perhaps if there are only a few breaking changes we could prioritize > > > > reviewing those first and leave the rest for 6.1. Alternatively, we > > > could > > > > release what's available now as 6.0 and release all the patches in a > > > couple > > > > months as 7.0. > > > > > > I wouldn't force our users to rename all their import statements in a > > > couple of month as we release BCEL 7.0 with breaking changes because we > > > didn't want to handle a known issue for BCEL 6.0. > > > > > > Let's settle this now. > > > > > > > +1 > > > > > > > > > > Emmanuel Bourg > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > -- > > http://people.apache.org/~britter/ > > http://www.systemoutprintln.de/ > > http://twitter.com/BenediktRitter > > http://github.com/britter > > > > > > -- > about.me/benmccann > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
