You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "justin georgeson (JIRA)" <ji...@apache.org> on 2016/07/20 14:20:20 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15385928#comment-15385928 ] 

justin georgeson commented on MNG-5913:
---------------------------------------

This ticket is about the uniqueness requirement for _project.repositories.repository.id_ and the complication with have to duplicate server authentication credentials in settings.xml to match each and every such repository id, even though the credentials might be the same for all those repositories? If so then I concur that it's confusing and the credentials should be decoupled. My preference would be to implement MNG-5585.

> 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)