[I previously posted this to the moribund [EMAIL PROTECTED] list. Don't know what I was thinking :-)]
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. 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. 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? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
