On Tue, Sep 06, 2005 at 10:52:06AM -0400, Andy Glick wrote: > [I previously posted this to the moribund [EMAIL PROTECTED] list. > Don't know what I was thinking :-)]
From what I can tell you haven't posted anything to that list and this question should be asked on that list. > I have just built and deployed the commons-attributes plugin in my local > repository, and last week I built and deployed the maven-hibernate-plugin. > I noticed that in each case the groupId was not org.apache.maven.plugins as > expected, but was instead org.codehaus.mojo, which is inherited from the > parent pom. I modified the pom of each plugin by adding a groupId element > whose value is org.apache.maven.plugins following the plugin's artifactId. Why? The groupId of these projects should be org.codehaus.mojo. > In the maven2 repository at Ibiblio, I don't see org.codehaus.mojo as an > existing location, but I do see 2 empty locations for Mojo project plugins, > maven-commons-attributes-plugin and maven-jpox-plugin; and at > snapshots.maven.codehaus.org I see that a number of Mojo project plugins > are deployed into the org.apache.maven.plugins directory, and again > org.codehaus.mojo does not exist. As there haven't been a single release of any of the Plugins from Mojo they're not on ibiblio. They used to have the group id "org.apache.maven.plugins" because that was what maven assumed. They should not have that anymore. > If org.apache.maven.plugins is in fact the intended deployment location, > then shouldn't the pom of each plugin contain a groupId element declaring > same, or are there one or more aspects of plugin control/deployment that I > have overlooked in the documentation? Please see [1] for more details. If you find that the document is missing some information please let me know and I'll answer your questions and/or fill it out. [1]: http://mojo.codehaus.org/development/guidelines.html -- Trygve
signature.asc
Description: Digital signature
