Details
-
Type:
Bug
-
Status:
Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.9
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Sites & Reporting
-
Labels:None
-
Environment:Windows, JDK 1.6
-
Complexity:Intermediate
-
Number of attachments :
Description
I have a simple test project that declares the dashboard-maven-plugin (see http://mojo.codehaus.org/dashboard-maven-plugin/usage.html ).
Note that the usage does explicitly state that the Codehaus repository must be specified as a plugin repository...
However, according to: http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html
I'm pretty sure that Maven should be able to resolve the dashboard-maven-plugin from the central repo.
I validated that the dashboard-maven-plugin residing in central is indeed the same artifact as that which lives at the codehaus repository.
But as you can see from my attached test case, the codehaus mojo is NOT being resolved without the special plugin repository defined. When running
mvn dashboard:dashboard
, I get the following error message:
[INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'dashboard'. [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] The plugin 'org.apache.maven.plugins:maven-dashboard-plugin' does not exist or no valid version could be found [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Sat Jan 24 12:40:55 PST 2009 [INFO] Final Memory: 1M/254M [INFO] ------------------------------------------------------------------------
If you edit the pom.xml to uncomment out the plugin repository declaration for codehaus, it works as one would expect.
My understanding is that the only reason why the Dashboard Usage mentions their plugin repository is because the artifact was not available on the central repository – but it certainly is today.
I also thought that perhaps the maven-metadata.xml might be incorrect (perhaps the dashboard plugin prefix is missing or different). I checked:
- http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml
- http://repository.codehaus.org/org/codehaus/mojo/maven-metadata.xml
and they both look OK to me... I clearly see:
<plugin> <name>Maven Dashboard Report Plugin</name> <prefix>dashboard</prefix> <artifactId>dashboard-maven-plugin</artifactId> </plugin>
And I don't see any plugin with a dashboard prefix specified as an Apache Maven Plugin here:
If I explicitly specify the dashboard plugin like:
mvn org.codehaus.mojo:dashboard-maven-plugin:dashboard
that works...
Overall, I am recording a bug because the documentation states:
Maven will always search the following groupId's after searching any plugin groups specified in the user's settings:
- org.apache.maven.plugins
- org.codehaus.mojo
I don't see this being done.
Finally, I even tried adding a pluginGroups to my settings.xml:
<pluginGroups> <pluginGroup>org.codehaus.mojo</pluginGroup> </pluginGroups>
But that did not work either...
Activity
I used find in the browser, it appears doesn't work on rendered xml files 
Does it also appear in your local repository at the same location? If so, it should certainly work.
this is because the mojo is not listed here:
http://repo2.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml
for it to work from the command-line without a metadata entry, it must be listed in the <build> section, not the <reporting> section (which is only triggered during the 'site' lifecycle).