[
https://issues.apache.org/jira/browse/MRESOLVER-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775009#comment-17775009
]
Slawomir Jaranowski commented on MRESOLVER-377:
-----------------------------------------------
{quote}
Maven does not have to make use of this (setting updatePolicy ==
metadataUpdatePolicy results in functionality like today, where there is only
one policy).
{quote}
[~cstamas] - So what is use case to have separate policy for metadata?
> Introduce metadata update policy
> --------------------------------
>
> Key: MRESOLVER-377
> URL: https://issues.apache.org/jira/browse/MRESOLVER-377
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.0
>
>
> Basically double the update policy, from RemoteRepository all way where
> needed, and make Resolver support separate "data" updatePolicy and "metadata"
> updatePolicy.
> Maven does not have to make use of this (setting updatePolicy ==
> metadataUpdatePolicy results in functionality like today, where there is only
> one policy).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
