commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben McCann <...@benmccann.com>
Subject Re: [VOTE] Release BCEL 6.0 based on RC3
Date Thu, 19 Feb 2015 22:51:00 GMT
Is BCEL-209 the only pending issue that would break binary compatibility?
Perhaps we could prioritize the issues that would break compatibility.
On Thu, Feb 19, 2015 at 7:19 AM, Benedikt Ritter <britter@apache.org> wrote:

> 2015-02-19 16:14 GMT+01:00 Ben McCann <ben@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.


No, it does not. We can release a new major version without a new package
name and new maven coords IFF the new version is binary compatible.

Gary



> 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 <britter@apache.org>
> > wrote:
> >
> > > 2015-02-19 16:06 GMT+01:00 Emmanuel Bourg <ebourg@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-unsubscribe@commons.apache.org
> > > > For additional commands, e-mail: dev-help@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
>



--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message