Hi all, Thanks for the clarification! Simo http://people.apache.org/~simonetripodi/ http://www.99soft.org/
On Wed, Jul 21, 2010 at 9:49 PM, sebb <seb...@gmail.com> wrote: > On 21 July 2010 20:40, Jochen Wiedmann <jochen.wiedm...@gmail.com> wrote: >> On Wed, Jul 21, 2010 at 9:36 PM, Simone Tripodi >> <simone.trip...@gmail.com> wrote: >> >>> * the parent POM is still referenced at version 15; >>> * the groupId is still commons-digester and not yet org.apache.commons. >>> >>> Should that data be modified? >> >> Change the parent POM: Yes. > > Agreed. > >> Change the groupId: Most definitely not. This would be an incompatible >> change and might break build systems like Maven, Ivy, etc. > > Certainly one cannot change the groupID in a minor release. > > Changing groupId in a major release is potentially possible, > especially if there are big API or package name changes. > In that case it's almost like releasing a brand new component, as the > users would have to make major changes anyway. > >> Jochen >> >> >> -- >> Germanys national anthem is the most boring in the world - how telling! >> >> --------------------------------------------------------------------- >> 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
