On 1 Sep 2014, at 03:21, Mark Gibson wrote:
> Ok, thanks Robert.
>
> Sadly this doesn't fit my expectations or needs. I'll look to do something a
> little more manual.
Are you perhaps mixing up tagging and branching?
What you describe sounds like what release:prepare would do.
Regards,
Grah
ase Plugin - release:branch: branch versions not set as
expected
Hi,
IMO branches are mutable, so it makes sense that this will always result in a
-SNAPSHOT Only tags are considered immutable, so that will get a NON Snapshot.
IIRC only the versions of one of the poms will be updated, either the one
stay
Hi,
IMO branches are mutable, so it makes sense that this will always result
in a -SNAPSHOT
Only tags are considered immutable, so that will get a NON Snapshot.
IIRC only the versions of one of the poms will be updated, either the one
staying on the trunk or the one moved to the branch.
th
(please see bottom of email for environment/version information)
I am trying to use the "release:branch" goal to create a branch, setting the
version in the POMs in both the new branch and the working copies. No matter
what properties I define on the command line, the release plugin is overridi
