You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Julian C. Dunn" <Ju...@cbc.ca> on 2005/09/22 15:58:33 UTC
wagon jar groupId -- why org.apache.maven?
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?
- Julian
--
-- Julian C. Dunn, P.Eng. <Ju...@cbc.ca> <jd...@nm.cbc.ca>
-- Platform Administrator, CBC.ca Production & Operations
-- Office: 2C310-Q * Tel.: (416) 205-3311 x5592 * Fax: (416) 205-7539
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: wagon jar groupId -- why org.apache.maven?
Posted by Trygve Laugstøl <tr...@codehaus.org>.
On Thu, 2005-09-22 at 16:38 -0400, Julian C. Dunn wrote:
> 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?
http://www.ibiblio.org/maven/org.apache.maven.wagon/
http://www.ibiblio.org/maven2/org/apache/maven/wagon/
> So Maven 1 and 2 repos are supposed to be incompatible, right?
Not "supposed to", but yes they are incompatible. Maven 2 can read from
Maven 1 repositories, Maven 1.1 will probably include support for
reading from Maven 2 repositories and artifacts deployed to the Maven 2
repository will be copied over to the Maven 1 repository.
So all in all, no big deal and it allows us to take a new (and required)
step with the capabilities of our repository.
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: wagon jar groupId -- why org.apache.maven?
Posted by "Julian C. Dunn" <Ju...@cbc.ca>.
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. <Ju...@cbc.ca> <jd...@nm.cbc.ca>
-- Platform Administrator, CBC.ca Production & Operations
-- Office: 2C310-Q * Tel.: (416) 205-3311 x5592 * Fax: (416) 205-7539
Re: wagon jar groupId -- why org.apache.maven?
Posted by Trygve Laugstøl <tr...@codehaus.org>.
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/
--
Trygve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org