jira-importer opened a new issue, #200: URL: https://github.com/apache/maven-deploy-plugin/issues/200
**[Alberto Gallardo](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=argr...@gmail.com)** opened **[MDEPLOY-315](https://issues.apache.org/jira/browse/MDEPLOY-315?redirect=false)** and commented Rewrite [usage#the-deploy-deploy-mojo|[https://maven.apache.org/plugins/maven-deploy-plugin/usage.html#the-deploy-deploy-mojo ](https://maven.apache.org/plugins/maven-deploy-plugin/usage.html#the-deploy-deploy-mojo)] to clarify that the distributionManagement can be also configured without modifying the `pom`. Currently, the documentation states: > To enable this mojo to function, you must include a valid \<distributionManagement/> section POM, [...] Suggesting that the pom must specify this element and must be modified accordingly. This suggestion is reinforced in [deploy-mojo#altDeploymentRepository](https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#altDeploymentRepository) : > #### **<altDeploymentRepository>** > > Specifies an alternative repository to which the project artifacts should be deployed (other than those specified in \<distributionManagement>). > (my interpretation is that `distributionManagement` must be present) Unfortunately, this mislead me to think that the only way to provide this configuration was by modifying the pom. I later found that `altDeploymentRepository` could be used **instead of** the `distributionManagement` in the pom. --- No further details from [MDEPLOY-315](https://issues.apache.org/jira/browse/MDEPLOY-315?redirect=false) -- 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: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
