[
http://jira.codehaus.org/browse/MNG-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4274:
-----------------------------------
Description:
An excerpt from a plugin's dependency tree
{noformat}
[INFO] org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.2
[INFO] +- org.apache.maven:maven-plugin-api:jar:2.0:compile
[INFO] +- org.apache.maven:maven-project:jar:2.0:compile
[INFO] | +- org.codehaus.plexus:plexus-utils:jar:1.0.4:compile
{noformat}
Note that the plugin has an indirect dependency on plexus-utils:1.0.4 via
maven-project.
Maven curently filters out core artifacts and their transitive dependencies
from the plugin realm. Given the above example, this also removes plexus-utils
from the plugin artifacts. Maven 2.x injects plexus-utils:1.1 instead, Maven
3.x injects the plexus-utils from its distro. In both cases, the plugin ends up
with a different version of plexus-utils than it was compiled/tested with,
giving rise to linkage errors or wrong plugin behavior.
The issue is theoretically not limited to plexus-utils but it's the most
prominent example.
was:
An excerpt from a plugin's dependency tree
{noformat}
[INFO] org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.2
[INFO] +- org.apache.maven:maven-plugin-api:jar:2.0:compile
[INFO] +- org.apache.maven:maven-project:jar:2.0:compile
[INFO] | +- org.codehaus.plexus:plexus-utils:jar:1.0.4:compile
{noformat}
Note that the plugin has an indirect dependency on plexus-utils:1.0.4 via
maven-project.
Maven 3 curently filters out core artifacts and their transitive dependencies
from the plugin realm. This removes plexus-utils from the plugin artifacts,
making the plugin use the plexus-utils version that ships with the core instead
of the one the plugin was compiled/tested with.
Affects Version/s: (was: 3.0-alpha-2)
2.0.6
Summary: Plugins with an undeclared but transitive dependency on
plexus-utils via a core artifact get wrong version of p-u (was: [regression]
Plugins with an undeclared but transitive dependency on plexus-utils get wrong
version of p-u)
> Plugins with an undeclared but transitive dependency on plexus-utils via a
> core artifact get wrong version of p-u
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-4274
> URL: http://jira.codehaus.org/browse/MNG-4274
> Project: Maven 2
> Issue Type: Bug
> Components: Class Loading, Plugins and Lifecycle
> Affects Versions: 2.0.6
> Reporter: Benjamin Bentmann
>
> An excerpt from a plugin's dependency tree
> {noformat}
> [INFO] org.apache.maven.plugins:maven-resources-plugin:maven-plugin:2.2
> [INFO] +- org.apache.maven:maven-plugin-api:jar:2.0:compile
> [INFO] +- org.apache.maven:maven-project:jar:2.0:compile
> [INFO] | +- org.codehaus.plexus:plexus-utils:jar:1.0.4:compile
> {noformat}
> Note that the plugin has an indirect dependency on plexus-utils:1.0.4 via
> maven-project.
> Maven curently filters out core artifacts and their transitive dependencies
> from the plugin realm. Given the above example, this also removes
> plexus-utils from the plugin artifacts. Maven 2.x injects plexus-utils:1.1
> instead, Maven 3.x injects the plexus-utils from its distro. In both cases,
> the plugin ends up with a different version of plexus-utils than it was
> compiled/tested with, giving rise to linkage errors or wrong plugin behavior.
> The issue is theoretically not limited to plexus-utils but it's the most
> prominent example.
--
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
