cstamas commented on code in PR #2080:
URL: https://github.com/apache/maven-resolver/pull/2080#discussion_r3892656479
##########
maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultArtifactResolver.java:
##########
@@ -119,6 +119,23 @@ public class DefaultArtifactResolver implements
ArtifactResolver {
public static final boolean DEFAULT_SIMPLE_LRM_INTEROP = false;
+ /**
+ * Configuration to restore the legacy "existence check" behavior for
artifacts that are present in the local
+ * repository but were cached from a remote repository unavailable in the
current build context: when enabled, a
+ * bare remote existence check (no content transfer, hence no checksum
validation) suffices to re-label the cached
+ * bytes as originating from the queried repository. When disabled (the
default), the artifact is downloaded again
+ * through the regular transfer path, so the content is validated against
the repository's checksum policy before
+ * it is registered with the local repository for that repository.
Enabling this trades integrity for bandwidth
+ * and is warmly recommended to leave it disabled.
+ *
+ * @configurationSource {@link
RepositorySystemSession#getConfigProperties()}
+ * @configurationType {@link java.lang.Boolean}
+ * @configurationDefaultValue {@link #DEFAULT_EXISTENCE_CHECK_RELABEL}
+ */
+ public static final String CONFIG_PROP_EXISTENCE_CHECK_RELABEL =
CONFIG_PROPS_PREFIX + "existenceCheckRelabel";
Review Comment:
How does this differ from "simple LRM interop"?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
