[
https://issues.apache.org/jira/browse/MNG-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952455#comment-17952455
]
Slawomir Jaranowski commented on MNG-5913:
------------------------------------------
{quote}
3.9.10 has already so many tickets and this is a big one I'd move it to 3.9.11.
{quote}
You are right that we have many changes for 3.9.10, for me this one will be
very useful.
I'm ready to take a risk also for it, even we have many other changes
I will ask about testing 3.9.10-SNAPSHOT on mailing list, we will see how
feedback will be
In the worst case we release 3.9.11 with fixes
> Allow to define aliases for existing server configurations in settings.xml
> --------------------------------------------------------------------------
>
> Key: MNG-5913
> URL: https://issues.apache.org/jira/browse/MNG-5913
> Project: Maven
> Issue Type: Improvement
> Components: Artifacts and Repositories, Deployment, Documentation:
> General, Settings
> Affects Versions: 3.3.3
> Reporter: Stanislav Spiridonov
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.9.10, 4.0.0-rc-4
>
>
> Now the repository (and other server related tags!!!) linked with
> corresponding server configuration by ID tag. For the complex project it
> produce tens of similar servers->server records in settings.xm
> The best explanation of the issue is on
> http://stackoverflow.com/questions/15011250/maven-meaning-of-repository-id
> The possible solution is define aliase for existing server configuration
> instead of duplicate it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
