Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6
-
Fix Version/s: 2.0.7
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
currently the mojo.codehaus.org is used if a plugin name conflicts with maven.apache.org. It should be the other way around.
Issue Links
| This issue duplicates: | ||||
| MNG-980 | Provide control over precedence of org.apache.maven.plugins group in search path |
|
|
|
| This issue relates to: | ||||
| MDEP-91 | org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin |
|
|
|
| MNG-2432 | Apache and Mojo plugins take precendence over plugins in the pom. |
|
|
|
created it0119 to check this and applied fix to 2.0.7-SNAPSHOT and trunk. I also found that the pluginGroups in the settings wasn't being searched prior to the defaults either (docs say it should). This is also fixed.