Try release:prepare release:perform -Dtag=3.0-b01 -Darguments=-Dtag=3.0-b01
You probably don't need a dedicated branch.
Am 19.02.2012 16:11 schrieb "Dipl.-Ing. Torsten Liermann" <
l...@liermann-it.de>:
>
> Yes, it is unfortunately.
> But, when release:branch ask me for the pom version of the bran
Yes, it is unfortunately.
But, when release:branch ask me for the pom version of the branch, the pom will
have exactly this version string (without the SNAPSHOT extension).
I think, i will hack the release plugin for me.
my use case for reaching a fix version without affecting the development o
Am 19.02.2012 01:29 schrieb "Dipl.-Ing. Torsten Liermann" <
l...@liermann-it.de>:
>
> Hi, (sorry, I can't speak english :( )
>
> I would like to create a branch with a release version in all pom's
>
> The Snapshot version of the trunk is 3.0.2-SNAPSHOT and the release
version should be 3.0-b01.
C
Looks like you are fighting maven (a loosing battle)
Only tags should have a fixed version
Sent from my iPhone
On 19 Feb 2012, at 00:29, "Dipl.-Ing. Torsten Liermann"
wrote:
> Hi, (sorry, I can't speak english :( )
>
> I would like to create a branch with a release version in all pom's
>
>
Hi, (sorry, I can't speak english :( )
I would like to create a branch with a release version in all pom's
The Snapshot version of the trunk is 3.0.2-SNAPSHOT and the release version
should be 3.0-b01.
Calling maven with
mvn org.apache.maven.plugins:maven-release-plugn:2.2.2:branch
-DbranchN
