Validate tagBase before starting -------------------------------- Key: MRELEASE-445 URL: http://jira.codehaus.org/browse/MRELEASE-445 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: prepare, scm Affects Versions: 2.0-beta-9 Reporter: Baptiste MATHUS Priority: Minor
Please note I'm using Subversion. I guess this tagBase validation isn't necessary with some other systems (like the old CVS). Currently, Maven-release-plugin proceeds this way: # Modify the current pom # Commit it # Tag it (say copy it under the tagBase) # Go back to next dev version The thing is: if the tagBase directory doesn't exist (forgotten or because of a typo in the pom), release:prepare will fail when trying to tag ALTHOUGH it already has committed the modified version :-/. I think that before starting prepare (or at least, there should be an option for it), release-plugin should check (using a "svn list [tagBase]" for example, in the case of Subversion) it the given tagBase exists. It would prevent from surely going into the wall when the tagBase is actually incorrect. Thanks a lot! Cheers. -- 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