[jira] Commented: (MNG-3383) Downloaded plugin dependencies influence project dependencies

["Jason van Zyl (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204593#action_204593 ] 

Jason van Zyl commented on MNG-3383:
------------------------------------

Application and plugin repositories are fully partitioned in 3.0.

> Downloaded plugin dependencies influence project dependencies
> -------------------------------------------------------------
>
>                 Key: MNG-3383
>                 URL: http://jira.codehaus.org/browse/MNG-3383
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, Plugins and Lifecycle
>    Affects Versions: 2.0.8
>            Reporter: Stefan Seidel
>             Fix For: 3.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