[MNG-7770] Implement workaround for MNG-7758/MRESOLVER-335
- 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-7770](https://issues.apache.org/jira/browse/MNG-7770?redirect=false)** and commented
Details see tickets.
---
**Affects:** 3.8.8, 3.9.1, 4.0.0-alpha-5
**Sub-tasks:**
- [MNG-7771](https://issues.apache.org/jira/browse/MNG-7771) Don't use ArtifactResolutionException#getMessage() w/o knowing whether there are other exceptions or not
**Issue Links:**
- [MNG-7758](https://issues.apache.org/jira/browse/MNG-7758) o.e.aether.resolution.ArtifactResolutionException incorrectly examined when multiple repositories are involved
(_**"is caused by"**_)
- [MRESOLVER-335](https://issues.apache.org/jira/browse/MRESOLVER-335) Better resolver errors for Artifact Not Found
(_**"is caused by"**_)
- [DOXIASITETOOLS-303](https://issues.apache.org/jira/browse/DOXIASITETOOLS-303) Implement workaround for MNG-7758/MRESOLVER-335
**Backported to:** [3.9.x-candidate](https://github.com/apache/maven/milestone/112?closed=1)
Contributor guide
Research direction
Start by reading the linked MNG-7758 and MRESOLVER-335 tickets, then review sub-task MNG-7771 for the specific exception-handling requirement. The issue indicates that a workaround is needed for resolver errors and that it was backported to the 3.9.x-candidate milestone; completion should address those linked cases.
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
- Needs clarification
- Newbie friendliness
- 25/100