[
https://issues.apache.org/jira/browse/MRESOLVER-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738792#comment-17738792
]
ASF GitHub Bot commented on MRESOLVER-377:
------------------------------------------
cstamas commented on code in PR #308:
URL: https://github.com/apache/maven-resolver/pull/308#discussion_r1247189892
##########
maven-resolver-api/src/main/java/org/eclipse/aether/RepositorySystemSession.java:
##########
@@ -94,7 +94,7 @@ public interface RepositorySystemSession {
String getChecksumPolicy();
/**
- * Gets the global update policy. If set, the global update policy
overrides the update policies of the remote
+ * Gets the global data update policy. If set, the global update policy
overrides the update policies of the remote
Review Comment:
IMHO, "data", as we call consequently the other "metadata" everywhere. Yes,
in resolver, "data" is "artifact", but the point is, it does not have to be
only that. Hence I went with generic "data" and "metadata".
> Introduce metadata update policy
> --------------------------------
>
> Key: MRESOLVER-377
> URL: https://issues.apache.org/jira/browse/MRESOLVER-377
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.14
>
>
> 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)
