Alternatively you might consider moving all components to the new groupId "org.apache.commons" and using maven's relocation (http://maven.apache.org/guides/mini/guide-relocation.html) to ensure backward compatibility.
SaM On Tue, Jun 16, 2009 at 8:58 AM, sebb<seb...@gmail.com> wrote: > On 15/06/2009, Jörg Schaible <joerg.schai...@gmx.de> wrote: >> Emmanuel Bourg wrote: >> >> > sebb a écrit : >> >> Which is the correct style for Maven2 releases? >> >> >> >> <groupId>org.apache.commons</groupId> >> >> <artifactId>commons-component</artifactId> >> >> >> >> or >> >> >> >> <groupId>commons-component</groupId> >> >> <artifactId>commons-component</artifactId> >> >> >> >> There are recent examples of both. >> > >> > I would say: >> > >> > - new components use "org.apache.commons" >> > >> > - already released components keep the same groupId. If the release is >> > incompatible with the previous one, switch from commons-component to >> > org.apache.commons. >> >> >> +1 >> > > Is there a good place to document this, e.g. on the Commons parent web-site? > Or at least on the Wiki? > >> - Jörg >> >> >> >> --------------------------------------------------------------------- >> 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
