This is an automated email from the ASF dual-hosted git repository.

slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 34301f5e Limit the Maven 3.9 notes on aliases and repositoryOrigins to 
3.9.16
34301f5e is described below

commit 34301f5e18e73650459272bced1337a61a9599f0
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Wed Nov 4 16:58:52 2026 +0000

    Limit the Maven 3.9 notes on aliases and repositoryOrigins to 3.9.16
    
    Both elements are now on maven-3.9.x (apache/maven#13826), so the notes
    hold for 3.9.16 and earlier only.
---
 content/markdown/settings.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/markdown/settings.md b/content/markdown/settings.md
index 96c3487d..c80b012c 100644
--- a/content/markdown/settings.md
+++ b/content/markdown/settings.md
@@ -212,8 +212,8 @@ declared in `settings.xml`: you can see them with `mvn 
help:effective-settings`.
 An alias must not be empty, and it should be unique across all server IDs
 and aliases. Otherwise Maven reports a warning.
 
-Maven 3.9 does not know `aliases`: it warns about an `Unrecognised tag` and 
ignores them, so a repository that
-uses an alias as its ID gets no credentials, and a server that requires them 
answers with status 401.
+Maven 3.9.16 and earlier do not know `aliases`: they warn about an 
`Unrecognised tag` and ignore them, so a
+repository that uses an alias as its ID gets no credentials, and a server that 
requires them answers with status 401.
 
 #### Server Repository Origins
 
@@ -264,8 +264,8 @@ its credentials may be used with:
 The declared origins are added to the origins Maven finds from repositories 
and mirrors.
 Nothing is replaced, so existing configurations keep working.
 Servers created from [aliases](#Server_Aliases) get the same 
`repositoryOrigins`.
-Maven 3.9 warns about an `Unrecognised tag` and ignores `repositoryOrigins`, 
so it keeps sending credentials by
-server ID only.
+Maven 3.9.16 and earlier warn about an `Unrecognised tag` and ignore 
`repositoryOrigins`, so they keep sending
+credentials by server ID only.
 Maven 4.0.0-rc-7 and earlier release candidates do not support 
`repositoryOrigins` either. They skip the element
 and report only "1 problem was encountered while building the effective 
settings"; run Maven with `-e` to see the
 `Unrecognised tag`. Use Maven 3.10.0 or a later Maven 4 release for 
`repositoryOrigins`.

Reply via email to