jira-importer commented on issue #511: URL: https://github.com/apache/maven-deploy-plugin/issues/511#issuecomment-2771547740
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented > 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. > 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
