[jira] Commented: (MRELEASE-106) Remember the Dry Run Status
[ http://jira.codehaus.org/browse/MRELEASE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96260 ] Mark Hobson commented on MRELEASE-106: -- Perhaps dryRun should become part of the ReleaseDescriptor? Remember the Dry Run Status --- Key: MRELEASE-106 URL: http://jira.codehaus.org/browse/MRELEASE-106 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-4 Environment: Release plugin snapshot 20060509.101136-3, Subversion Reporter: Bob Allison Priority: Minor 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-106) Remember the Dry Run Status
[ http://jira.codehaus.org/browse/MRELEASE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96263 ] Emmanuel Venisse commented on MRELEASE-106: --- I'm not sure it's a good idea, but don't know yet why. Remember the Dry Run Status --- Key: MRELEASE-106 URL: http://jira.codehaus.org/browse/MRELEASE-106 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-4 Environment: Release plugin snapshot 20060509.101136-3, Subversion Reporter: Bob Allison Priority: Minor 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-106) Remember the Dry Run Status
[ http://jira.codehaus.org/browse/MRELEASE-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96269 ] Mark Hobson commented on MRELEASE-106: -- It would be handy in the case of release:rollback: 1) mvn release:prepare -DdryRun=true 2) mvn release:rollback (2) would perform live SCM operations once MRELEASE-229 is fixed, if dryRun=true wasn't explicitly set. Storing dryRun in the release.properties would allow these second-phase goals to inherit the same environment. Remember the Dry Run Status --- Key: MRELEASE-106 URL: http://jira.codehaus.org/browse/MRELEASE-106 Project: Maven 2.x Release Plugin Issue Type: Improvement Affects Versions: 2.0-beta-4 Environment: Release plugin snapshot 20060509.101136-3, Subversion Reporter: Bob Allison Priority: Minor 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
