[ https://issues.apache.org/jira/browse/MNG-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899125#comment-17899125 ]
Tamas Cservenak commented on MNG-8380: -------------------------------------- Seems Maven 3.9.9 is "resilient", in a way it just reports a warning: {noformat} [cstamas@angeleyes maven (master)]$ mvn validate [WARNING] [WARNING] Some problems were encountered while building the effective settings [WARNING] Unrecognised tag: 'aliases' (position: START_TAG seen ...</id>\n <aliases>... @13:16) @ /home/cstamas/.m2/settings.xml, line 13, column 16 [WARNING] [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: ... {noformat} > Allow Repositories and Mirrors To Delegate Credentials To A <server> > -------------------------------------------------------------------- > > Key: MNG-8380 > URL: https://issues.apache.org/jira/browse/MNG-8380 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories, Settings > Affects Versions: 3.9.9 > Reporter: Robert Krajewski > Priority: Major > Labels: DRY, credentials, mirror, mirrorOf, repository, servers, > settings > > As far as I can tell from the current documentation and the behavior of Maven > 3.9.9, mirrors and repositories need authentication are still obliged to rely > on a server element of the same id as the repository for each repository or > mirror that needs credentials. If this is not the case, please document a > solution that does not require such repetition, otherwise please take a look > at the discussion at > [https://stackoverflow.com/questions/17511469/setting-a-single-server-credentials-in-maven-for-multiple-repositories] > If there is no proposal, what I'd suggest is that an element like > <referenceServerId> (or something like that) contained in a <mirror> or > <repository> element, which if present, directs Maven to use the credentials > used in the referenced <server> with the <id> given by <referenceServerId>. > That server *must* be present in the settings environment. Otherwise the > older behavior of using a <server> with the same <id> as the mirror or > repository applies. -- This message was sent by Atlassian Jira (v8.20.10#820010)