[MNG-7018] Maven does not traverse all repos when downloading extensions from .mvn/extensions.xml
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** opened **[MNG-7018](https://issues.apache.org/jira/browse/MNG-7018?redirect=false)** and commented
Check out Maven from `MNG-6114`. Run Core ITs, see MNG-5771 fail. (Compare uploaded log files and settings). MNG-6114 orders all settings elements from global to local. I.e., repos from global settings come first. Here is the bug: One expects Maven to traverse all available repos to download artifacts, but Maven stops here with the first one. W/o MNG-6114 it works accidently because Central override was servered by a mirror.
---
**Affects:** 3.6.3
**Attachments:**
- [master.log](https://issues.apache.org/jira/secure/attachment/13015236/master.log) (_2.63 kB_)
- [master-settings.xml](https://issues.apache.org/jira/secure/attachment/13015234/master-settings.xml) (_2.03 kB_)
- [MNG-6114.log](https://issues.apache.org/jira/secure/attachment/13015235/MNG-6114.log) (_10.58 kB_)
- [MNG-6114-settings.xml](https://issues.apache.org/jira/secure/attachment/13015233/MNG-6114-settings.xml) (_2.03 kB_)
**Issue Links:**
- [MNG-6114](https://issues.apache.org/jira/browse/MNG-6114) Elements from the global settings should be ordered before elements from the user settings
(_**"is caused by"**_)
- [MNG-5984](https://issues.apache.org/jira/browse/MNG-5984) Maven core extension resolution ignores repositories from activeByDefault profiles in settings.xml
Contributor guide
Research direction
Check out Maven from MNG-6114 and run the Core ITs, focusing on the MNG-5771 failure. Compare master.log, MNG-6114.log, and the two settings XML attachments to trace repository ordering and extension resolution. Done means Maven traverses all available repositories when downloading extensions from .mvn/extensions.xml.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100