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

**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** opened **[MNG-7094](https://issues.apache.org/jira/browse/MNG-7094?redirect=false)** and commented

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.

---

**Affects:** 3.6.3

**Issue Links:**
- [MNG-5663](https://issues.apache.org/jira/browse/MNG-5663) [regression] resolution of import-scoped transitive dependencies ignores additional repositories

- [MNG-3220](https://issues.apache.org/jira/browse/MNG-3220) Allow managed dependencies to be imported into other projects

- [MNG-6772](https://issues.apache.org/jira/browse/MNG-6772) Super POM overwrites remapped central repository in nested dependencyManagement import POMs

- [MNG-6397](https://issues.apache.org/jira/browse/MNG-6397) Maven Transitive Dependency Resolution Does Not Respect Repository Definition in pom.xml

1 votes, 2 watchers