On 22 August 2014 11:51, Gary Gregory <garydgreg...@gmail.com> wrote: > I do not think we should change the maven coordinates if the package name > does not change.
Agreed. > Sebb, can you clarify? Maven identifies the code by means of the Maven coordinates; it does not look at package names. Java identifies classes by means of the package name. There must be a 1-1 mapping between the two, otherwise classpath issues can result for Maven projects. i.e. if the package is changed, the coords must be changed and vice-versa. > Gary > > <div>-------- Original message --------</div><div>From: Stefan Bodewig > <bode...@apache.org> </div><div>Date:08/22/2014 06:12 (GMT-05:00) > </div><div>To: Commons Developers List <dev@commons.apache.org> > </div><div>Subject: Re: [BCEL] Trying a release? </div><div> > </div>On 2014-08-22, Benedikt Ritter wrote: > >> Okay... TBH, I don't like that BCEL is treated special. Looks like a >> different versioning schema to me. Also other groupId and artifactId. But >> if you RM, it's your decision :-) I won't block a release because of this >> if BCEL was always released like this. > > BCEL used to be a Jakarta Projects of its own rather than a Commons > component, hence the historically different coordinates. > > If BCEL6 can be used as a drop in replacement, then not changing the > coordinates might be a good idea (but begs the question of why it has a > new major version). Gump says current BCEL trunk works for Xalan and > Ant - at least to the extent their builds are using it. > > Stefan > > --------------------------------------------------------------------- > 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
