The idea is vice versa: Do not change the groupId, unless you are considering changes as serious as changing the package name.
On Mon, Aug 16, 2010 at 1:06 PM, Niall Pemberton <niall.pember...@gmail.com> wrote: > On Mon, Aug 16, 2010 at 11:43 AM, Jochen Wiedmann > <jochen.wiedm...@gmail.com> wrote: >> Not that I have any ideas about Commons Net: But to me the first >> requirement would be a change of the package structure like moving to >> o.a.c.net2, rather than o.a.c.net. Otherwise the groupId should >> preferrably be stable. > > IMO the build tool/repository should not play any part in deciding > package names. Changing the package name of a component should be > based purely on things like compatibility. > > Niall > >> Jochen >> >> >> On Mon, Aug 16, 2010 at 12:30 PM, sebb <seb...@gmail.com> wrote: >>> Net is still using the commons-net Maven groupId. >>> >>> What needs to be done to move it to the o.a.c groupId? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- I Am What I Am And That's All What I Yam (Popeye) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
