Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0-alpha-4
-
Fix Version/s: 2.0
-
Component/s: resolve-plugins
-
Labels:None
-
Number of attachments :
Description
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.
Issue Links
| This issue is related to: | ||||
| MNG-2926 | group search order for plugins is inverted |
|
|
|
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: