gnodet commented on code in PR #13005:
URL: https://github.com/apache/maven/pull/13005#discussion_r3908825030


##########
maven-core/src/main/java/org/apache/maven/internal/aether/DefaultRepositorySystemSessionFactory.java:
##########
@@ -109,6 +112,24 @@ public class DefaultRepositorySystemSessionFactory {
      */
     private static final String MAVEN_REPO_LOCAL_RECORD_REVERSE_TREE = 
"maven.repo.local.recordReverseTree";
 
+    /**
+     * User property selecting how server credentials configured in settings 
are scoped to repositories:
+     * <ul>
+     *     <li>{@code origin} (default): credentials for a server id are only 
used with a repository whose
+     *     origin (protocol, host and port) matches a repository or mirror 
declared with the same id in
+     *     settings or on the command line. For server ids without any such 
declared repository (for
+     *     example pure deployment servers whose URL comes from the project's
+     *     {@code distributionManagement}), credentials are used as before, 
but a warning identifying the
+     *     target origin is emitted.</li>
+     *     <li>{@code strict}: like {@code origin}, but credentials are 
refused for server ids that have no
+     *     repository or mirror declared in settings or on the command 
line.</li>
+     *     <li>{@code id}: legacy behavior, credentials are matched by server 
id only.</li>
+     * </ul>
+     *
+     * @since 3.9.10
+     */
+    public static final String MAVEN_REPOSITORY_CREDENTIAL_SCOPE = 
"maven.repository.credentialScope";

Review Comment:
   ```suggestion
        * @since 3.9.17
   ```
   Maven 3.9.10 was already released and does not contain this constant. The 
sibling PR #12954 correctly uses `@since 3.10.0`. This should reference the 
next 3.9.x milestone (`3.9.17`).



-- 
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]

Reply via email to