[
https://issues.apache.org/jira/browse/MNG-5913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14962320#comment-14962320
]
Michael Osipov edited comment on MNG-5913 at 10/18/15 12:16 PM:
----------------------------------------------------------------
I agree, it is confusing and counter-intuitive. The accepted answer is right. I
had this recently at work where several sites have their own hosted repos on
the same server with the same logins. Duplicating config is simply stupid. One
would actually need aliases, though that would require a model change...
Please note that the SO question is obsolete because repos in POMs are
deprecated and you shall your mirrors in your settings.xml via a repo manager.
was (Author: michael-o):
I agree, it is confusing and counter-intuitive. The accepted answer is right. I
had this recently at work where several sites have the own hosted repos on the
same server with the same logins. Duplicating configs is simply stupid. One
would actually need aliases. Though that would require a model change...
Plase that the SO question is obsolete because repos in POMs are deprecated and
you shall your mirros in settings.xml via a repo manager.
> Add to repository reference to server configuration
> ---------------------------------------------------
>
> Key: MNG-5913
> URL: https://issues.apache.org/jira/browse/MNG-5913
> Project: Maven
> Issue Type: Improvement
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
