[ https://issues.apache.org/jira/browse/MRESOLVER-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak updated MRESOLVER-369: -------------------------------------- Fix Version/s: (was: 1.9.11) > Expose configuration for update check manager where to apply policy > ------------------------------------------------------------------- > > Key: MRESOLVER-369 > URL: https://issues.apache.org/jira/browse/MRESOLVER-369 > Project: Maven Resolver > Issue Type: New Feature > Components: Resolver > Reporter: Tamas Cservenak > Assignee: Tamas Cservenak > Priority: Major > > Currently, DefaultUpdateCheckManager ALWAYS applies policy to both, artifacts > and metadata. This causes problems when we want to "discover new versions" > (or similar use case, that relies on fresh metadata), but metadata is never > updated due remote repository update policy of "never", so only -U make it > work as expected. -U OTOH is like shooting with cannon onto bird, as it > updates many many more as well, not only the one metadata we are interested > in. > Moreover, since Maven3 artifacts are immutable. > So, add a config like {{aether.updateCheckManager.applyUpdatePolicy}} that > accepts values "all" (like today) and "metadata" (does not applies policy to > artifacts, if artifact present, no update needed). -- This message was sent by Atlassian Jira (v8.20.10#820010)