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.
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
, I get the following error message:
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:
and they both look OK to me... I clearly see:
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:
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:
I don't see this being done.
Finally, I even tried adding a pluginGroups to my settings.xml:
But that did not work either...