Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0-beta-1
-
Fix Version/s: 2.0.7
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
settings.xml has a <pluginGroups> section to list additional groupIds to search for top level m2 plugin goals.
By default, "org.apache.maven.plugins" is not required to be present in this list, and always wins if there is a collision.
<pluginGroups> that explicitly list "org.apache.maven.plugins" should be able to control this default behavior, so that a different plugin groupId can always win in the case of a collision.
For example, in settings.xml:
<pluginGroups>
<pluginGroup>org.example.maven.plugins</pluginGroup>
<pluginGroup>org.apache.maven.plugins</pluginGroup>
</pluginGroups>
This would allow "org.example.maven.plugins" to always win in the case of a collision, whereas:
<pluginGroups>
<pluginGroup>org.example.maven.plugins</pluginGroup>
</pluginGroups>
would still allow "org.apache.maven.plugins" to always win, as it does today.
Issue Links
| This issue is duplicated by: | ||||
| MNG-2926 | group search order for plugins is inverted |
|
|
|
From working with Maven2.0 RC it seems that the <pluginGroups> are ignored altogether.
Following the example in
http://www.codehaus.org/~jvanzyl/maven2/guides/plugin/guide-java-plugin-development.html
the plugin group "sample.plugin" is completely ignored in the settings.xml.