Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.4
-
Fix Version/s: 2.1.0, 3.0-alpha-2
-
Component/s: None
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
When resolving plugin prefixes, plugins from apache and mojo take precendence over plugins explicitly in the pom.xml. For example, an old plugin with prefix "jetty" at org.codehaus.mojo.jetty-maven-plugin is always used in preference to the new maven-jetty-plugin with prefix "jetty", even though it is specified in the pom like so:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.0-SNAPSHOT</version>
</plugin>
Issue Links
| This issue is related to: | ||||
| MNG-2926 | group search order for plugins is inverted |
|
|
|
Note that I removed the codehaus plugin from http://www.ibiblio.org/maven2/org/codehaus/mojo/maven-metadata.xml
There was an entry
<plugin>
<name>Maven2 Jetty plugin</name>
<prefix>jetty</prefix>
<artifactId>jetty-maven-plugin</artifactId>
</plugin>
althought there was no jetty-maven-plugin folder that was enough to make maven fail