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 1eff2224 Say what Maven 3.9 does with server aliases and repository
origins
1eff2224 is described below
commit 1eff22245e293bd8fc40e2f28ff9c10d2a3a1553
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Mon Nov 2 13:09:27 2026 +0000
Say what Maven 3.9 does with server aliases and repository origins
---
content/markdown/settings.md | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/content/markdown/settings.md b/content/markdown/settings.md
index e61f2129..747c49c3 100644
--- a/content/markdown/settings.md
+++ b/content/markdown/settings.md
@@ -212,6 +212,9 @@ 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.
+
#### Server Repository Origins
Since Maven 3.10.0 and 4.0.0, the credentials of a server are bound to the
origins
@@ -261,6 +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.
When a server has at least one origin, from repositories, mirrors or
`repositoryOrigins`, its credentials are
not sent to a repository with the same ID at another origin.