[
https://issues.apache.org/jira/browse/MNG-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281496#comment-17281496
]
Herve Boutemy commented on MNG-7094:
------------------------------------
[import-scoped dependencies (in
dependencyManagement)|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies]
are downloaded by Model Builder during effective POM calculation.
It's completely different from "normal" dependencies (in dependencies, with
transitive management), which are downloaded by build lifecycle when required,
far later
no surprise that algorithm may differ
no idea if model builder could be updated to take reactor POM/project into
account...
at least this difference should be explained (like here, but more on the site)
> Assure in an IT that reactor repository definitions do not leak into import
> dependencies
> ----------------------------------------------------------------------------------------
>
> Key: MNG-7094
> URL: https://issues.apache.org/jira/browse/MNG-7094
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories, Dependencies, Design,
> Patterns & Best Practices, Integration Tests
> Affects Versions: 3.6.3
> Reporter: Michael Osipov
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> Based on several discussions (MNG-6772, MNG-6397) the topic of repo scoping
> causes a lot of confusion.
> Create an IT which shows that repositories defined in a reactor are never
> available (leak) to imported dependency BOMs. Thus all repos are properly
> scoped.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
