You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Graham Leggett (JIRA)" <ji...@codehaus.org> on 2007/05/11 18:17:12 UTC
[jira] Created: (MDEP-91) org.codehaus.mojo:dependency-maven-plugin
takes precedence over org.apache.maven.plugins:maven-dependency-plugin
org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin
----------------------------------------------------------------------------------------------------------------
Key: MDEP-91
URL: http://jira.codehaus.org/browse/MDEP-91
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: resolve-plugins
Affects Versions: 2.0-alpha-4
Reporter: Graham Leggett
Assignee: Brian Fox
Priority: Critical
When an attempt is made to configure the org.apache.maven.plugins:maven-dependency-plugin, maven resolves the org.codehaus.mojo:dependency-maven-plugin plugin instead.
As a result of the different plugin config syntax, execution fails.
According to available docs and Google, specifying absolute behaviour when a plugin namespace clash occurs is either not possible, or not documented.
--
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: (MDEP-91) org.codehaus.mojo:dependency-maven-plugin
takes precedence over org.apache.maven.plugins:maven-dependency-plugin
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MDEP-91.
-------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha-5
website updated
> org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MDEP-91
> URL: http://jira.codehaus.org/browse/MDEP-91
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: resolve-plugins
> Affects Versions: 2.0-alpha-4
> Reporter: Graham Leggett
> Assignee: Brian Fox
> Priority: Critical
> Fix For: 2.0-alpha-5
>
>
> When an attempt is made to configure the org.apache.maven.plugins:maven-dependency-plugin, maven resolves the org.codehaus.mojo:dependency-maven-plugin plugin instead.
> As a result of the different plugin config syntax, execution fails.
> According to available docs and Google, specifying absolute behaviour when a plugin namespace clash occurs is either not possible, or not documented.
--
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: (MDEP-91)
org.codehaus.mojo:dependency-maven-plugin takes precedence over
org.apache.maven.plugins:maven-dependency-plugin
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95697 ]
Brian Fox commented on MDEP-91:
-------------------------------
This is fixed in Maven 2.0.7, but you're correct I should add a FAQ. http://jira.codehaus.org/browse/MNG-2926
> org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MDEP-91
> URL: http://jira.codehaus.org/browse/MDEP-91
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: resolve-plugins
> Affects Versions: 2.0-alpha-4
> Reporter: Graham Leggett
> Assignee: Brian Fox
> Priority: Critical
>
> When an attempt is made to configure the org.apache.maven.plugins:maven-dependency-plugin, maven resolves the org.codehaus.mojo:dependency-maven-plugin plugin instead.
> As a result of the different plugin config syntax, execution fails.
> According to available docs and Google, specifying absolute behaviour when a plugin namespace clash occurs is either not possible, or not documented.
--
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: (MDEP-91)
org.codehaus.mojo:dependency-maven-plugin takes precedence over
org.apache.maven.plugins:maven-dependency-plugin
Posted by "Graham Leggett (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MDEP-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95682 ]
Graham Leggett commented on MDEP-91:
------------------------------------
According to some info on the users list, the plugin can be absolutely specified like this:
mvn org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:unpack
Ideally the maven-dependency-plugin site / FAQ should be changed to include:
- The fact there is a namespace clash between dependency-maven-plugin and maven-dependency-plugin.
- The fact that it can be worked around by specifying the plugin goal absolutely as abaove.
> org.codehaus.mojo:dependency-maven-plugin takes precedence over org.apache.maven.plugins:maven-dependency-plugin
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MDEP-91
> URL: http://jira.codehaus.org/browse/MDEP-91
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: resolve-plugins
> Affects Versions: 2.0-alpha-4
> Reporter: Graham Leggett
> Assignee: Brian Fox
> Priority: Critical
>
> When an attempt is made to configure the org.apache.maven.plugins:maven-dependency-plugin, maven resolves the org.codehaus.mojo:dependency-maven-plugin plugin instead.
> As a result of the different plugin config syntax, execution fails.
> According to available docs and Google, specifying absolute behaviour when a plugin namespace clash occurs is either not possible, or not documented.
--
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