[MNG-7094] Assure in an IT that reactor repository definitions are not used when Model Builder downloads dependencies with scope import

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.6.3
• Fix Version/s: 4.0.x-candidate
• Component/s: Artifacts and Repositories, Dependencies, Design, Patterns & Best Practices, Integration Tests
• Labels: must-be-in-4.0.0-alpha-2
• Assignee: Unassigned
• Reporter: Michael Osipov
• Created: 08/Feb/21 14:40
• Updated: 02/Mar/22 20:18

Description

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 (inject) to download imported dependency BOMs. Thus all repos are properly scoped.

Issue Links

• is related to: MNG-6772 Super POM overwrites remapped central repository in nested dependencyManagement import POMs
• is related to: MNG-6397 Maven Transitive Dependency Resolution Does Not Respect Repository Definition in pom.xml
• relates to: MNG-5663 [regression] resolution of import-scoped transitive dependencies ignores additional repositories
• relates to: MNG-3220 Allow managed dependencies to be imported into other projects