[MNG-5913] Allow to define aliases for existing server configurations in settings.xml

[jira-importer]

Stanislav Spiridonov opened MNG-5913 and commented

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.

---

Affects: 3.3.3

Issue Links:

• MNG-6895 Add aliasing feature for settings.xml:///servers/server
  ("is duplicated by")

• MNG-8381 Allow server.aliases in settings.xml
  ("is duplicated by")

• MNG-5615 Rework credentials handling

• MNG-8380 Allow Repositories and Mirrors To Delegate Credentials To A <server>

Remote Links:

• GitHub Pull Request #2333
  
• GitHub Pull Request #2346
  

Backported to: 3.9.x-candidate

3 votes, 5 watchers

[jira-importer]

Michael Osipov commented

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.

[jira-importer]

Stanislav Spiridonov commented

The SO is just illustrate the issue. Actually I use the the server configuration for deployment and mirror so at least 5 servers with the same content.

[jira-importer]

Michael Osipov commented

Though, I understand your request, would you kindly rephrase the title and description? It is not clear to other readers in the first place.

[jira-importer]

justin georgeson commented

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.

[jira-importer]

Michael Osipov commented

This one must remain for various reasons. I also requires a rework of the settings.xml. I have the same server credentials several times because of different server ids.

[jira-importer]

Michael Osipov commented

3.9.10 has already so many tickets and this is a big one I'd move it to 3.9.11.

[jira-importer]

Slawomir Jaranowski commented

3.9.10 has already so many tickets and this is a big one I'd move it to 3.9.11.

 
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 

[jira-importer]

Michael Osipov commented

I am fine with that. I prefer reliability/stability over features.

[jira-importer]

Slawomir Jaranowski commented

As new questions and doubts was appeared I will move it for 3.9-candidate. 
First we will deliver it for 4.x