You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/20 14:47:00 UTC
[jira] [Resolved] (MNG-5913) Allow to define aliases for existing
server configurations in settings.xml
[ https://issues.apache.org/jira/browse/MNG-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Elliotte Rusty Harold resolved MNG-5913.
----------------------------------------
Resolution: Won't Do
> 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
> Priority: Major
>
> 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.3.4#803005)