You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Bartel (JIRA)" <ji...@codehaus.org> on 2006/07/11 14:23:22 UTC
[jira] Created: (MNG-2432) Apache and Mojo plugins take precendence
over plugins in the pom.
Apache and Mojo plugins take precendence over plugins in the pom.
-----------------------------------------------------------------
Key: MNG-2432
URL: http://jira.codehaus.org/browse/MNG-2432
Project: Maven 2
Type: Bug
Versions: 2.0.4
Reporter: Jan Bartel
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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2432) Apache and Mojo plugins take precendence
over plugins in the pom.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-2432:
-----------------------------------
Fix Version/s: 2.1.0
Merged to 2.1.x in [r751248|http://svn.eu.apache.org/viewvc?view=rev&revision=751248].
> Apache and Mojo plugins take precendence over plugins in the pom.
> -----------------------------------------------------------------
>
> Key: MNG-2432
> URL: http://jira.codehaus.org/browse/MNG-2432
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Jan Bartel
> Assignee: Brian Fox
> Fix For: 2.1.0, 3.0-alpha-2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2432) Apache and Mojo plugins take
precendence over plugins in the pom.
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2432?page=comments#action_69506 ]
Carlos Sanchez commented on MNG-2432:
-------------------------------------
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
> Apache and Mojo plugins take precendence over plugins in the pom.
> -----------------------------------------------------------------
>
> Key: MNG-2432
> URL: http://jira.codehaus.org/browse/MNG-2432
> Project: Maven 2
> Type: Bug
> Versions: 2.0.4
> Reporter: Jan Bartel
>
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2432) Apache and Mojo plugins take precendence
over plugins in the pom.
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-2432:
-------------------------------
Fix Version/s: 2.1-alpha-1
> Apache and Mojo plugins take precendence over plugins in the pom.
> -----------------------------------------------------------------
>
> Key: MNG-2432
> URL: http://jira.codehaus.org/browse/MNG-2432
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Jan Bartel
> Fix For: 2.1-alpha-1
>
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2432) Apache and Mojo plugins take precendence
over plugins in the pom.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MNG-2432.
--------------------------
Assignee: Brian Fox
Resolution: Fixed
Fix Version/s: (was: 2.1-alpha-1)
2.0.7
> Apache and Mojo plugins take precendence over plugins in the pom.
> -----------------------------------------------------------------
>
> Key: MNG-2432
> URL: http://jira.codehaus.org/browse/MNG-2432
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Jan Bartel
> Assignee: Brian Fox
> Fix For: 2.0.7
>
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2432) Apache and Mojo plugins take precendence
over plugins in the pom.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-2432:
-----------------------------------
Affects Version/s: 3.0-alpha-2
Preferring plugins from the POM over those from the plugin groups in the settings wasn't fixed until 3.x.
> Apache and Mojo plugins take precendence over plugins in the pom.
> -----------------------------------------------------------------
>
> Key: MNG-2432
> URL: http://jira.codehaus.org/browse/MNG-2432
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Jan Bartel
> Assignee: Brian Fox
> Fix For: 3.0-alpha-2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2432) Apache and Mojo plugins take precendence
over plugins in the pom.
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-2432:
-----------------------------------
Affects Version/s: (was: 3.0-alpha-2)
Fix Version/s: (was: 2.0.7)
3.0-alpha-2
> Apache and Mojo plugins take precendence over plugins in the pom.
> -----------------------------------------------------------------
>
> Key: MNG-2432
> URL: http://jira.codehaus.org/browse/MNG-2432
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.0.4
> Reporter: Jan Bartel
> Assignee: Brian Fox
> Fix For: 3.0-alpha-2
>
>
> 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>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira