-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[MNG-7802][MNG-7803] Fix behaviour of the maven update policy (draft) #1144
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
base: master
Are you sure you want to change the base?
Conversation
97f9e60 to
d0189a3
Compare
|
But
Reasoning: This PR makes -U not override anymore the "remembered to fail" of resolver in local repo, as shown in ITs. "Remembered to fail" when resolver emits |
551e03f to
aae2a17
Compare
7c90865 to
efbf354
Compare
efbf354 to
f49ed2a
Compare
|
Will update the PR when apache/maven-resolver#297 is released. |
|
To be done in resolver 2.0.0, please once out upgrade to this instead https://issues.apache.org/jira/browse/MRESOLVER-377 |
|
Resolve #9189 |
JIRA issue: MNG-7802
After several iterations, this PR simply provides a custom
UpdateCheckManagerwhich can implement the desired policy : artifacts are considered immutable once downloaded from a repository. TheupdatePolicydefined in repositories affect the metadata retrieval only, i.e. checks forLATEST,SNAPSHOT, and more generally all version resolution requests.This PR also fix the CLI options as part of MNG-7803:
-nsu,--no-snapshot-updatesand--update-snapshotsoption-U-/--update-always,-un/--update-never,-ud/--update-daily,-up/--update-policy` CLI options