Maven plugin prefix resolution doesn't seem to work as expected

[Orton K Randy]

Hello,
I've created a MOJO for a specific application need. I've followed maven's guidelines in naming the plugin so that I didn't have to mention the full
mvn groupId:artifactId:version:goal
for executing my plugin(I've named it to match the format ${prefix}-maven-plugin). I've even included the 'goalPrefix' property in the plugin POM's configuration section. Here's a sniff of what I did to my plugin's POM:
<configuration> <goalPrefix>${prefix}</goalPrefix> </configuration>
But I'm still unable to execute my plugin just using mvn ${prefix}:goal since it complains it can't find the plugin in any repository. I've still had to use mvn groupId:artifactId:version:goal Any idea why?

[Peter Johnson]

You need one more thing. In you settings.xml file, add the following:

  <pluginGroups>
    <pluginGroup>your-group-id</pluginGroup>
  </pluginGroups>

Without this, Maven doesn't know to look into that groupId to find additional plugins.

[Orton K Randy]

True, maven only seems to recognize plugins that belong to maven/codehaus groupIds. So I've had to add my plugin group specification to the settings xml. Not that I'm ok with doing so, but I don't have a choice right now. Cheers for the info, mate.