[
https://jira.codehaus.org/browse/MDEPLOY-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360541#comment-360541
]
Robert Scholte commented on MDEPLOY-164:
----------------------------------------
bq. For uploading of artifact, problem is the same, but is there any solution ?
The concept is that in the {{pom.xml}} of the Maven project you specify which
is its master repository for this artifact, in other words: where to upload it
to. It is a project specific configuration, hence it is specified in the
{{pom.xml}}, since your team should always deploy to the same repository. And
when working on different project and different repositories, you can't trust
someones personal configuration in the {{settings.xml}} which contains system
configuration.
A good practice is to have a company-parent pom (or project-parent pom,
depending on the way you work), which contains very global configuration, such
as the distribution-management to the Nexus hosted repository.
bq. The fact that mirrors are meant for downloading only doesn't seems to be
documented (http://maven.apache.org/guides/mini/guide-mirror-settings.html).
Good point, I'll add it.
> Mirrors defined in settings.xml should be used to upload artifacts
> ------------------------------------------------------------------
>
> Key: MDEPLOY-164
> URL: https://jira.codehaus.org/browse/MDEPLOY-164
> Project: Maven Deploy Plugin
> Issue Type: Improvement
> Components: deploy:deploy, deploy:deploy-file
> Affects Versions: 2.7
> Environment: Maven 3.1.0, Maven 3.0.5, Windows
> Reporter: Rémi Alvergnat
> Assignee: Robert Scholte
> Priority: Minor
>
> When a mirror is defined in maven settings.xml for a repository declared in
> distributionManagement, upload of artifacts should be done using the mirror
> URL, instead of original URL from the repository.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
