On 14 February 2012 08:50, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi al guys, > > current 2.0 trunk has been updated to fully support Generics[1], > adding improvement as discussed on 2011 in ML - there is the cost > anyway of losing the backward compatibility, clirr detects 57 errors. > > So, according to what we already experienced (digester3 ,pool2), I > would proceed on updating the package to o.a.c.chain2, groupId to > o.a.c. and artifactId commons-chain2.
There's no need to update both the groupId and tthe artifactId. So long as the each unique package name relates to a unique groupId:artifactId pair, Maven should be able to resolve dependencies correctly. However it is easier to keep the artifactId in step with the package name. > Any objection? Changing package name causes lots of work for downstream users. So are you sure that: - compatibilty has to be broken in order to support the changes that have been made? - there aren't any other pending API changes that would require another package rename for the next release? > TIA, > -Simo > > [1] https://issues.apache.org/jira/browse/CHAIN-58 > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > --------------------------------------------------------------------- > 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
