[
https://issues.apache.org/jira/browse/MNG-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8381:
---------------------------------
Description:
To allow setup like this:
{noformat}
<settings>
<servers>
<server>
<id>oss.sonatype.org</id>
<aliases>
<alias>plexus-release</alias>
<alias>takari-release</alias>
</aliases>
...
</server>
</servers>
</settings>
{noformat}
This way pretty much the validation remains same (server.id is unique), but the
search for server entry would need to modify and consider aliases as well.
This would not work with Maven3 plugins (running in compat mode), but Resolver
can make use of this extra info.
was:
To allow setup like this:
{noformat}
<settings>
<servers>
<server>
<id>oss.sonatype.org</id>
<aliases>
<alias>plexus-release</alias>
<alias>takari-release</alias>
</aliases>
...
</server>
</servers>
</settings>
{noformat}
> Allow server.aliases in settings.xml
> ------------------------------------
>
> Key: MNG-8381
> URL: https://issues.apache.org/jira/browse/MNG-8381
> Project: Maven
> Issue Type: Improvement
> Components: Settings
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-beta-6
>
>
> To allow setup like this:
> {noformat}
> <settings>
> <servers>
> <server>
> <id>oss.sonatype.org</id>
> <aliases>
> <alias>plexus-release</alias>
> <alias>takari-release</alias>
> </aliases>
> ...
> </server>
> </servers>
> </settings>
> {noformat}
> This way pretty much the validation remains same (server.id is unique), but
> the search for server entry would need to modify and consider aliases as well.
> This would not work with Maven3 plugins (running in compat mode), but
> Resolver can make use of this extra info.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
