On Thu, 2005-09-22 at 21:52 +0200, Trygve Laugstøl wrote: > On Thu, 2005-09-22 at 09:58 -0400, Julian C. Dunn wrote: > > I noticed that the Maven Wagon JARs that are depended upon by such > > things as the artifact plugin belong to the groupId > > org.apache.maven.wagon. Is this the new standard for naming groupIds? > > What was the rationale for changing this, and are other Apache projects > > doing the same? > > As far as I can remember that has been the group id since we started > building Wagon and SCM with Maven 2. The new more verbose naming > convention was needed to make it easier to organize the artifacts (and > as a side-effect it gives Ibiblio some help in that the index page won't > list nearly as much directories :) > > Hopefully most people and projects (include the Apache ones) will see > the benefits of this new layout and start using it. I've already seen > quite a few projects that's using the new naming convention [1,2] > > [1]: http://www.ibiblio.org/maven2/org/ > [1]: http://www.ibiblio.org/maven2/net/
Ok, fair enough... just so I have this straight, the wagon artifacts compatible with a Maven 1 repository would reside under: <repo-root>/org.apache.maven.wagon/<something>.jar whereas with a Maven 2 repository would now be: <repo-root>/org/apache/maven/wagon/<something>.jar? So Maven 1 and 2 repos are supposed to be incompatible, right? - Julian -- -- Julian C. Dunn, P.Eng. <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- Platform Administrator, CBC.ca Production & Operations -- Office: 2C310-Q * Tel.: (416) 205-3311 x5592 * Fax: (416) 205-7539
signature.asc
Description: This is a digitally signed message part
