Actually it was a typo in my mail.. our releases have the form of 1.0.0.Wxx
(as in 1.0.0.W44)
Would this be ok ?
Michael McCallum-3 wrote:
I would highly recommend that you tag your projects X.Y and when you build
branches introduce the .Z
maven treats the -SSS specially and makes it
Hi guys,
We have a multi-module project; we are using 1.0.0-SNAPSHOT as version for
every module. We are trying to have a release at the end of every week, so
our releases get the following form: 1.0.0-Wxx. In time we realized we need
to branch the project before releasing it so we have some time
Actually it's working fine... I was able to do the branch, after many hours
of pain...
The problem that I noticed is that , if there is even a small problem during
the release:branch, I'm being left with all the changes commited in
Subversion. Of course, mvn release:rollback doesn't work so I'm
I would highly recommend that you tag your projects X.Y and when you build
branches introduce the .Z
maven treats the -SSS specially and makes it less e.g.
X.Y.Z-A X.Y.Z
which obviously causes odd behaviour..
I use versions like 1.0, 1.1, 1.2
and patches being builds off branches being
This is the error I'm getting when doing a mvn release:rollback (after a mvn
release:branch).
Did anybody encountered this specific error before ?
..
[INFO]
[INFO] Building Maven 2 Example
[INFO]
Jim,
Sure we can work on that together. If you don't mind, I'll contact you on that
privately (don't need to send every single e-mail over the list).
I'll let you know when I start things up on my end, feel free to do the same!
On Thursday 26 April 2007 22:21, Crossley, Jim wrote:
Thanks
On Thursday 26 April 2007 22:38, Crossley, Jim wrote:
Hi.
Rapha l Pi roni [EMAIL PROTECTED] writes:
[...]
is this dumb?
Nope.
Definitely not dumb!
do that need a enhancement jira?
Yep. http://jira.codehaus.org/browse/MRELEASE-226
Not sure about this though.. I think it should be
I'll look at the issue created by Jim, but it was in my planning to implement
the branch creation in the next month.
Emmanuel
Roland Asmann a écrit :
Jim,
Sure we can work on that together. If you don't mind, I'll contact you on that
privately (don't need to send every single e-mail over
On 4/27/07, Emmanuel Venisse [EMAIL PROTECTED] wrote:
I'll look at the issue created by Jim, but it was in my planning to implement
the branch creation in the next month.
Emmanuel
There is another, slightly related issue. From time to time, you want
to merge the bug fixes from the
Branching (as I've stated a couple of time now) is an issue, which I feel can
and should be automated. However, the merging of code is something that I
feel should be left with manual intervention.
Some bugs that have been fixed in a branch, may have been solved in the head
already by e.g.
On 4/27/07, Roland Asmann [EMAIL PROTECTED] wrote:
Branching (as I've stated a couple of time now) is an issue, which I feel can
and should be automated. However, the merging of code is something that I
feel should be left with manual intervention.
Some bugs that have been fixed in a branch,
I used the release plugin to successfully release version 2.0.2.1 of our
project. We continued working on the HEAD targeting version 2.0.3 while
QA tested 2.0.2.1. To address bugs reported against that release, we
created a 2.0.2 branch in CVS. We applied our fixes there.
Now it's time to
On 4/26/07, Crossley, Jim [EMAIL PROTECTED] wrote:
I used the release plugin to successfully release version 2.0.2.1 of our
project. We continued working on the HEAD targeting version 2.0.3 while
QA tested 2.0.2.1. To address bugs reported against that release, we
created a 2.0.2 branch in
How did you use the release plugin? Unless I'm mistaken, proper use
of the plugin will result in a release being generated with fixed
version number, commit to SCM, then poms updated back to SNAPSHOT and
committed to SCM again.
I'm not currently using the release plugin myself so I'm not
: Releasing a branch?
How did you use the release plugin? Unless I'm mistaken, proper use
of the plugin will result in a release being generated with fixed
version number, commit to SCM, then poms updated back to SNAPSHOT and
committed to SCM again.
I'm not currently using the release plugin myself so I'm
-Original Message-
From: Trevor Spackman [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 1:12 PM
To: Maven Users List
Subject: RE: Releasing a branch?
I'm using the release plugin on a very regular basis, and it makes
things very smooth. When you release 1.0.1-SNAPSHOT, the plugin creates
Hi Jim,
I've been reading the replies you got, and I feel most of them didn't really
understand your problem.
I'm using the release-plugin as well, but I'll admit right away that I haven't
tried it on branches yet. I believe it wasn't really thought for that though.
At least, not
: Thursday, April 26, 2007 12:13 PM
To: Maven Users List
Subject: Re: Releasing a branch?
Hi Jim,
I've been reading the replies you got, and I feel most of them didn't really
understand your problem.
I'm using the release-plugin as well, but I'll admit right away that I haven't
tried it on branches
As I see it, you just described the only solution that works. I may be wrong
here, so if any of the maven-programmers think I am: please DO tell me!
No matter how you assign the version-numbers, fact remains that maven can
not 'automatically' handle branching.
I feel that there should be a
version, in this case the version has to be manually
updated on the branch.
Both approaches work, but there is some manual version editing in
both. Once the branching is done, the release plugin works fine on the
branch (for releasing further maintenance releases) and on the trunk
(for releasing
the branching is done, the release plugin works fine on the
branch (for releasing further maintenance releases) and on the trunk
(for releasing the next major release). The manual update is only
necessary once per branch.
-
To unsubscribe, e
Message-
From: Heinrich Nirschl [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 3:06 PM
To: Maven Users List
Subject: Re: Releasing a branch?
On 4/26/07, Roland Asmann [EMAIL PROTECTED] wrote:
As I see it, you just described the only solution that works. I may be
wrong here, so
Hi.
Rapha l Pi roni [EMAIL PROTECTED] writes:
[...]
is this dumb?
Nope.
do that need a enhancement jira?
Yep. http://jira.codehaus.org/browse/MRELEASE-226
Thanks,
Jim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
23 matches
Mail list logo
