[MNG-7062] Add first class support for deployment repositories to settings.xml

[jira-importer]

Phil Clay opened MNG-7062 and commented

The maven settings.xml file currently has first-class support for controlling artifact downloads via the mirrors section. It would be intuitive and logical if the the settings.xml file also had first-class support for controlling artifact uploads.

Being able to control both artifact uploads and downloads from the settings.xml file allows for easier centralized management in organizations using a repository manager, in which all downloads and uploads should go through the repository manager.

The current approach of being able to point artifact downloads to a repository manager in settings.xml, but not being able to point uploads to the same repository manager in settings.xml is clunky and not intuitive.

Here are several alternatives that can be used today, but none are as easy/intuitive as first class support in the settings.xml would be.

1. Define downloads in settings.xml file, but define uploads via distributionManagement in poms.
2. Define alt*DeploymentRepository properties in settings.xml (as mentioned in PR #23). Do not use distributionManagement in poms at all.
3. Define custom release/snapshot repo properties in settings.xml, and define a distributionManagement section in poms that references those properties

---

Affects: 3.6.3

[jira-importer]

Michael Osipov commented

Robert Scholte, Karl Heinz Marbaise, what is your opinion on this? This generally makes sense, but distribution management is not necesarily the opposite of repos...I am a bit split here.

[jira-importer]

Robert Scholte commented

I consider the distributionManagement as a part of the trace where artifacts are coming from, so it must be there, either in the POM or via inheritence.
So my first response would be no.
But with the build/consumer we can rewrite the POM, so we should be to inject this information while distributing the artifacts.

[jira-importer]

Michael Osipov commented

Robert Scholte, but why does this matter for the consumer then? The distro management is relevant during release only. Consumers don't need this kind of information.

[jira-importer]

Robert Scholte commented

Nobody can publish directly to central. If you have issues with some unfamiliar artifact, this could help you trace down its origin. That kind of information can be very valuable, even though it is not used dependency resolution.

[jira-importer]

Michael Osipov commented

OK, I see this makes sense of course. This piece of information needs to be retained.