[
https://issues.apache.org/jira/browse/MNG-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Clay updated MNG-7062:
---------------------------
Description:
The maven settings.xml file currently has first-class support for controlling
artifact _downloads_ via the [mirrors
section|https://maven.apache.org/settings.html#Mirrors]. 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.
# Define downloads in settings.xml file, but define uploads via
{{distributionManagement}} in poms.
# Define {{alt*DeploymentRepository}} properties in settings.xml (as mentioned
in [PR #23|https://github.com/apache/maven-site/pull/223]). Do not use
{{distributionManagement}} in poms at all.
# Define custom release/snapshot repo properties in settings.xml, and define a
{{distributionManagement}} section in poms that references those properties
was:
The maven settings.xml file currently has first-class support for controlling
artifact _downloads_ via the [mirrors
section|https://maven.apache.org/settings.html#Mirrors]. 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.
# Define downloads in settings.xml file, but define uploads via
{{distributionManagement}} in poms.
# Define {{alt*DeploymentRepository}} properties in settings.xml (as mentioned
in [PR #23|https://github.com/apache/maven-site/pull/223]. Do not use
{{distributionManagement}} in poms at all.
# Define custom release/snapshot repo properties in settings.xml, and define a
{{distributionManagement}} section in poms that references those properties
> Add first class support for deployment repositories to settings.xml
> -------------------------------------------------------------------
>
> Key: MNG-7062
> URL: https://issues.apache.org/jira/browse/MNG-7062
> Project: Maven
> Issue Type: Improvement
> Components: Settings
> Affects Versions: 3.6.3
> Reporter: Phil Clay
> Priority: Minor
>
> The maven settings.xml file currently has first-class support for controlling
> artifact _downloads_ via the [mirrors
> section|https://maven.apache.org/settings.html#Mirrors]. 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.
> # Define downloads in settings.xml file, but define uploads via
> {{distributionManagement}} in poms.
> # Define {{alt*DeploymentRepository}} properties in settings.xml (as
> mentioned in [PR #23|https://github.com/apache/maven-site/pull/223]). Do not
> use {{distributionManagement}} in poms at all.
> # Define custom release/snapshot repo properties in settings.xml, and define
> a {{distributionManagement}} section in poms that references those properties
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
