MRELEASE-484 and 485 say that I was using 2.0-beta-10 when I gave up.
On Fri, Oct 23, 2009 at 10:10 PM, Matt Milliss wrote:
> I've been trying to solve this exact same problem, it looks like a bug in
> the release plugin, what version are you using.
>
>
> On 15/10/2009 7:40 AM, Allan Ditzel wrote
I've been trying to solve this exact same problem, it looks like a bug
in the release plugin, what version are you using.
On 15/10/2009 7:40 AM, Allan Ditzel wrote:
Really? Were you running it from the location the trunk was checked out? For
us, if we do a mvn release:prepare in the location of
That recipe never occured to me. I just try to run it as I'd run the release
side of thing, and the results were chaotic.
On Wed, Oct 14, 2009 at 4:40 PM, Allan Ditzel wrote:
> Really? Were you running it from the location the trunk was checked out?
> For
> us, if we do a mvn release:prepare in t
Really? Were you running it from the location the trunk was checked out? For
us, if we do a mvn release:prepare in the location of the trunk, then
release:perform, and then cd into target/checkout and from there do mvn
release:branch -DbranchName=my-branch -DupdateBranchVersions=true
-DupdateWorkin
personally, I couldn' t get release:branch to work at all, interactively or
batch.
On Wed, Oct 14, 2009 at 2:23 PM, Allan Ditzel wrote:
> Hi,
>
> I'm trying to make a branch from a tag in batch mode using the release
> plugin. The pom in the tag has its version set to 0.2.0. I would like for
> th
Hi,
I'm trying to make a branch from a tag in batch mode using the release
plugin. The pom in the tag has its version set to 0.2.0. I would like for
the branch version to be 0.2.1-SNAPSHOT, however when I use the plugin it
always sets the branch version to 0.2.0-SNAPSHOT. However, in interactive
m
