Alberto Gallardo opened MDEPLOY-315 and commented
Rewrite [usage#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 :
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
Alberto Gallardo opened MDEPLOY-315 and commented
Rewrite [usage#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:
Suggesting that the pom must specify this element and must be modified accordingly. This suggestion is reinforced in deploy-mojo#altDeploymentRepository :
Unfortunately, this mislead me to think that the only way to provide this configuration was by modifying the pom. I later found that
altDeploymentRepositorycould be used instead of thedistributionManagementin the pom.No further details from MDEPLOY-315