[ 
https://issues.apache.org/jira/browse/MNG-4347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MNG-4347:
--------------------------------
    Comment: was deleted

(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #34 (See 
[https://builds.apache.org/job/maven-3.x%20Jigsaw/34/])
[MNG-4347] import-scoped dependencies of direct dependencies are not (schulte: 
rev c3a4bd14d235911a5425f5ec70d39bbcdcd39569)
* (edit) 
maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultModelResolver.java
)

> import-scoped dependencies of direct dependencies are not resolved using 
> profile modifications from settings.xml
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4347
>                 URL: https://issues.apache.org/jira/browse/MNG-4347
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Dependencies, General, 
> Profiles, Settings
>    Affects Versions: 2.2.1
>            Reporter: John Casey
>            Priority: Critical
>             Fix For: 2.2.2, 3.5.1-candidate
>
>
> Given:
> * project A lists project B as a dependency
> * project B lists project C as an import-scoped entry in dependencyManagement
> * project B's dependency version for project C is a SNAPSHOT
> * the user's settings.xml file modifies the definition of the central 
> repository to enable searching for SNAPSHOT artifacts.
> When project A's dependency POMs are retrieved as part of collecting the 
> transitive dependency closure for A, B's project instance is built. During 
> this process, the POM for project C should be retrieved from central 
> (according to the modifications in settings.xml). However, the profile 
> information from the settings.xml is never applied to project B's POM, and 
> never modifies the central repository definition found there. Since the 
> default definition for the repository 'central' from the super POM has 
> snapshots disabled, project C's POM cannot be found, and the build fails.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to