Alberto Gallardo created MDEPLOY-315: ----------------------------------------
Summary: Documentation Key: MDEPLOY-315 URL: https://issues.apache.org/jira/browse/MDEPLOY-315 Project: Maven Deploy Plugin Issue Type: Improvement Reporter: Alberto Gallardo 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: {quote}To enable this mojo to function, you must include a valid <distributionManagement/> section POM, [...] {quote} 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] : {quote} h4. *<altDeploymentRepository>* Specifies an alternative repository to which the project artifacts should be deployed (other than those specified in <distributionManagement>).{quote} (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. -- This message was sent by Atlassian Jira (v8.20.10#820010)