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 884353ca Say that Maven 4.0.0-rc-7 does not support repositoryOrigins
884353ca is described below

commit 884353ca70c4c5b706212beb6850f2b56f0bbeb7
Author: Sylwester Lachiewicz <[email protected]>
AuthorDate: Wed Nov 4 10:51:39 2026 +0000

    Say that Maven 4.0.0-rc-7 does not support repositoryOrigins
    
    The element reached the Maven 4 line after 4.0.0-rc-7 was tagged; rc-7
    skips it and names it only with -e.
---
 content/markdown/settings.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/markdown/settings.md b/content/markdown/settings.md
index 747c49c3..96c3487d 100644
--- a/content/markdown/settings.md
+++ b/content/markdown/settings.md
@@ -266,6 +266,9 @@ 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 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`.
 
 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.

Reply via email to