You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2009/07/01 19:08:05 UTC
[jira] Updated: (MNG-3383) Downloaded plugin dependencies influence
project dependencies
[ http://jira.codehaus.org/browse/MNG-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3383:
------------------------------
Fix Version/s: (was: 2.2.1)
2.2.x
not a high priority fix as pluginRepositories are deprecated
> Downloaded plugin dependencies influence project dependencies
> -------------------------------------------------------------
>
> Key: MNG-3383
> URL: http://jira.codehaus.org/browse/MNG-3383
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories, Dependencies, Plugins and Lifecycle
> Affects Versions: 2.0.8
> Reporter: Stefan Seidel
> Fix For: 2.2.x
>
> Attachments: pom.xml
>
>
> Currently, a plugin may define additional pluginRepositories, which are used to resolve dependencies of that plugin.
> This leads to the fact that a plugin might resolve a dependency which would normally not be available to the project.
> When it does that, it seems to write a metadata-central (although on the central repo this artifact does not exist) and thus, the project will use that dependency, too.
> How to reproduce:
> 1. remove xstream from local repo:
> {code}rm -Rf ~/.m2/repository/com/thoughtworks/xstream{code}
> 2. run mvn clean install on the attached pom.xml
> -> the build should fail because the version 1.3.0-SNAPSHOT is not available at repo1.maven.org
> 3. edit the pom.xml, uncomment the plugin definition (jspc used for demonstration purposes only)
> 3. run mvn clean install again
> -> the build succeeds and the 1.3.0-SNAPSHOT is being built into the artifact, which is wrong.
--
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