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

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.6.3
• Component/s: Settings
• Assignee: Unassigned
• Reporter: Phil Clay
• Created: 30/Dec/20 19:47
• Updated: 30/Dec/20 22:14

Description

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