[
https://jira.codehaus.org/browse/MRELEASE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297413#comment-297413
]
Robert Scholte commented on MRELEASE-752:
-----------------------------------------
There are several reasons why people don't run a {{release:perform}}: because
they don't have a repository manager and/or don't have a webcontainer for
site-deployment.
In these cases I'd advice to run the {{release:perform -Dgoals=install}} to
confirm that the tagged code is stable.
Because you can't predict this, I won't add this check. If this happens too
often, consider a company/organization parent-pom containing this configuration.
But... there's this wish to create a {{release:release}} goal which should
execute both the {{prepare}} and {{perform}}. In this case you know if
{{deploy}} will we called or not. So I'll leave this one open as a reminder.
> release:prepare should check for <distributionManagement>
> ---------------------------------------------------------
>
> Key: MRELEASE-752
> URL: https://jira.codehaus.org/browse/MRELEASE-752
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.2.2
> Reporter: Daniel Serodio
> Priority: Minor
>
> release:perform will fail if <distributionManagement> is not set, so
> release:prepare should check for this POM element and fail if it's not set.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
