maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Ribeiro (JIRA) <>
Subject [jira] Commented: (MNG-4001) Unable to resolve Dashboard mojo from Central
Date Tue, 15 Feb 2011 17:37:25 GMT


André Ribeiro commented on MNG-4001:

This should be fixed ASAP, some organizations cannot afford to switch to version 3 just like

> Unable to resolve Dashboard mojo from Central
> ---------------------------------------------
>                 Key: MNG-4001
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Sites & Reporting
>    Affects Versions: 2.0.9
>         Environment: Windows, JDK 1.6
>            Reporter: Anthony Whitford
>             Fix For: Issues to be reviewed for 3.x
>         Attachments:
> I have a simple test project that declares the dashboard-maven-plugin (see
> Note that the usage does explicitly state that the Codehaus repository must be specified
as a plugin repository...
> However, according to:
> 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 {noformat}mvn dashboard:dashboard{noformat},
I get the following error message:
> {noformat}
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dashboard'.
> [INFO] ------------------------------------------------------------------------
> [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] ------------------------------------------------------------------------{noformat}
> 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:{code:xml}
> <plugin>
>     <name>Maven Dashboard Report Plugin</name> 
>     <prefix>dashboard</prefix> 
>     <artifactId>dashboard-maven-plugin</artifactId> 
> </plugin>
> {code}
> And I don't see any plugin with a dashboard prefix specified as an Apache Maven Plugin
> *
> If I explicitly specify the dashboard plugin like:  {noformat}mvn org.codehaus.mojo:dashboard-maven-plugin:dashboard{noformat}
> that works...
> Overall, I am recording a bug because the [documentation|]
> 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 
> {quote}
> I don't see this being done.
> Finally, I even tried adding a {{pluginGroups}} to my {{settings.xml}}:{code:xml}
> <pluginGroups>
>   <pluginGroup>org.codehaus.mojo</pluginGroup>
> </pluginGroups>
> {code}
> But that did not work either...

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message