maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MNG-5913) Allow to define aliases for existing server configurations in settings.xml
Date Sun, 18 Oct 2015 12:52:05 GMT

     [ https://issues.apache.org/jira/browse/MNG-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Osipov updated MNG-5913:
--------------------------------
    Summary: Allow to define aliases for existing server configurations in settings.xml  (was:
Allows to define the aliases for existing server configuration in settings.xml)

> 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
>
> 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
(v6.3.4#6332)

Mime
View raw message