[MRELEASE-445] Validate tagBase before starting

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.0-beta-9
• Component/s: prepare, scm
• Assignee: Robert Scholte
• Reporter: Baptiste MATHUS
• Created: 01/May/09 13:52
• Updated: 06/Apr/15 01:08
• Resolved: 27/Feb/14 11:46

Description

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:

1. Modify the current pom
2. Commit it
3. Tag it (say copy it under the tagBase)
4. 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.

Issue Links

• depends upon: SCM-487 support --parents option for svn copy (tag commands) (svn 1.5 required)
• relates to: MRELEASE-512 SCM information should be validated