Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MRESOLVER-414] Fully split update policies internally #342

Merged
merged 4 commits into from Oct 15, 2023

Conversation

cstamas
Copy link
Member

@cstamas cstamas commented Oct 15, 2023

And externally provide means to not use this feature (to use them as one), basically to fall back to 1.x behavior.

The code was half-baked, so now resolver internally fully splits and maintaines two policies, one for artifacts and one for metadata. Still, on surface ther are getUpdatePolicy() and setUpdatePolicy() that makes resolver behave as before (as in 1.x).


https://issues.apache.org/jira/browse/MRESOLVER-414

…ovide means to not use this feature

The code was half-baked, so now resolver internally fully splits and maintaines two policies,
one for artifacts and one for metadata. Still, on surface ther are getUpdatePolicy() and
setUpdatePolicy() that makes resolver behave as before (as in 1.x).

---

https://issues.apache.org/jira/browse/MRESOLVER-414
@cstamas cstamas added this to the 2.0.0 milestone Oct 15, 2023
@cstamas cstamas self-assigned this Oct 15, 2023
@cstamas cstamas changed the title [MRESOLVER-414] Fully split update policies internally, externally pr… [MRESOLVER-414] Fully split update policies internally Oct 15, 2023
@cstamas cstamas merged commit af1a42f into apache:master Oct 15, 2023
10 checks passed
@cstamas cstamas deleted the MRESOLVER-414 branch October 15, 2023 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant