[
https://jira.codehaus.org/browse/MRELEASE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-445.
-----------------------------------
Resolution: Duplicate
Assignee: Robert Scholte
> Validate tagBase before starting
> --------------------------------
>
> Key: MRELEASE-445
> URL: https://jira.codehaus.org/browse/MRELEASE-445
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare, scm
> Affects Versions: 2.0-beta-9
> Reporter: Baptiste MATHUS
> Assignee: Robert Scholte
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
