[MNG-8020] Support new Resolve 2.0 split policies
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** opened **[MNG-8020](https://issues.apache.org/jira/browse/MNG-8020?redirect=false)** and commented
The MRESOLVER-377 in resolver 2.0 did split policies, Maven should use this. But, this requires model and many other changes, so consider when to do this. Current Maven4 code works in same way as Maven3 does, as Resolver 2.0 handles this (policy Maven sets is applied to both).
---
**Affects:** 4.0.x-candidate
Contributor guide
Research direction
Start by reviewing MRESOLVER-377 and how the current Maven 4 code applies policies through Resolver 2.0. Identify the model and other affected areas mentioned in the issue, then determine the required changes so Maven can use Resolver's split policies independently rather than applying one policy to both.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100