[m2] Installing plugins with different groupIds

[Mark Hobson]

Do you have to configure anything differently for m2 to auto-discover
plugins that aren't in the org.apache.maven.plugins groupId?  For
example, I have a simple plugin POM:

<project>
        <modelVersion>4.0.0</modelVersion>
        <groupId>a</groupId>
        <artifactId>a</artifactId>
        <packaging>maven-plugin</packaging>
        <version>1.0</version>
        <dependencies>
                <dependency>
                        <groupId>org.apache.maven</groupId>
                        <artifactId>maven-plugin-api</artifactId>
                        <version>2.0-beta-1-SNAPSHOT</version>
                </dependency>
        </dependencies>
</project>

A simple mojo:

/** @goal a */
public class AMojo extends AbstractMojo {
        public void execute() throws MojoExecutionException {
                getLog().info("--- A ---");
        }
}

I then "m2 -DupdateReleaseInfo=true install" it and try to run it with
"m2 a:a", but it only seems to look for a matching plugin within
org.apache.maven.plugins?  Also, the plugin-registry.xml even seems to
define it with that groupId:

    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-a-plugin</artifactId>
      <useVersion>RELEASE</useVersion>
    </plugin>

Am I missing anything obvious here?

Cheers,

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]