[
https://jira.codehaus.org/browse/MRELEASE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Roberge updated MRELEASE-106:
----------------------------------
Attachment: 0002-MRELEASE-106-Provided-reasonable-failure-message-whe.patch
I implemented a new perform phase to check whether dry run was set to true when
preparing release. This patch is dependent on the previous patch file.
I attempted to write an integration test using the invoker plugin, but
discovered it may not be possible because the build fails. From what I could
tell, the plugin is meant to verify successful builds. If anyone has a
suggestion for how I might go about writing an integration test for this, I'm
happy to look into it.
> Remember the Dry Run Status
> ---------------------------
>
> Key: MRELEASE-106
> URL: https://jira.codehaus.org/browse/MRELEASE-106
> Project: Maven 2.x Release Plugin
> Issue Type: Improvement
> Components: prepare
> Affects Versions: 2.0-beta-4
> Environment: Release plugin snapshot 20060509.101136-3, Subversion
> Reporter: Bob Allison
> Priority: Minor
> Labels: contributers-welcome
> Fix For: Backlog
>
> Attachments: 0001-MRELEASE-106-Remember-the-dry-run-status.patch,
> 0002-MRELEASE-106-Provided-reasonable-failure-message-whe.patch
>
>
> When doing a dry run of a release, make note of that in the
> release.properties file so that a reasonable "failure" can occur if the user
> tries to perform the release. Also, this flag might be used to allow a
> non-dry-run prepare to occur without needing to do a clean in between (maybe
> also not need to prompt but reuse the same answers as in the dry run).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
