You need to declare 'org.codehaus.cargo' as a pluginGroup in your
settings.xml:

  <pluginGroups>
    <pluginGroup>org.codehaus.cargo</pluginGroup>
  </pluginGroups>

/Anders

On Wed, Feb 9, 2011 at 15:31, Thorsten Heit <[email protected]> wrote:

> Hi,
>
> according to the Cargo docs "mvn cargo:help" prints a short description,
> but that seems to work only with Maven 2; with Maven 3 I'm getting the
> following error:
>
> (...)
> [ERROR] No plugin found for prefix 'cargo' in the current project and in
> the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available
> from the repositories [local (/home/thorsten/.m2/repository), central (
> http://10.26.31.180:8080/nexus/content/groups/public), snapshots (
> http://10.26.31.180:8080/nexus/content/repositories/apache-snapshots)] ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundForPrefixException
>
> To achieve the same I have to add both group Id and artifact Id in the
> command line, i.e. "mvn org.codehaus.cargo:cargo-maven2-plugin:help"
>
> Is there a better way? And why does Maven 2 find the plugin although
> according to the docs it searches for plugins in different groups, i.e.
> org.apache.maven.plugins and org.codehaus.mojo?
>
>
> Regards
>
> Thorsten
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to