Please create an issue for it. ping me back with the issue id and I'll add it to the Backlog
On 4 July 2011 22:48, Christopher Cudennec <[email protected]> wrote: > Thanks Stephen, that was a quick answer :) > > Checking if the tag exists seems to be described by: > http://jira.codehaus.org/browse/MRELEASE-572 and > http://jira.codehaus.org/browse/MRELEASE-165. I'd vote for these! > Unfortunately I could not find an issue for checking the release repository. > Do you know anything about that? Is it worth creating a new issue? > > Cheers, > > Christopher > > > Am 04.07.2011 23:22, schrieb Stephen Connolly: >> >> correct. See MRELEASE-166 and other open issues in the release plugin >> >> On 4 July 2011 22:07, Christopher Cudennec<[email protected]> wrote: >>> >>> Hi everyone! >>> >>> I'd like to have some advice for using the Maven release plugin. As far >>> as I >>> understand the plugin does not check the SCM or the Maven repository >>> before >>> performing a release. It will result in a failure if either the tag >>> already >>> exists in the SCM or the version has already been deployed to the >>> repository. In that case you have to clean up the mess yourself by >>> performing a rollback or removing the SCM tag. >>> Can someone confirm that behaviour? Is there any provided way to check >>> preconditions for performing the release *before* actually executing it? >>> >>> Thanks, >>> >>> Christopher >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
