Sorry, could not respond to this thread sooner...
Wendy Smoak wrote:
On Wed, Apr 28, 2010 at 10:23 AM, napple fabble jm.postili...@gmail.com
wrote:
The only thing I need to do is mvn release:prepare. This creates the
correct tag and updates trunk as I want it to. I haven't had any need
Tim O'Brien wrote:
mvn versions:set -DnewVersion=1.1-SNAPSHOT
Great and much simpler than I expected ;-)
Thanks (to both of you)
Jan
--
From address is valid until 01.06.2010
-
To unsubscribe, e-mail:
Don't forget to update the scm section in the pom.xml files
On 5 May 2010 08:38, Jan Torben Heuer jan_key67...@jtheuer.de wrote:
Tim O'Brien wrote:
mvn versions:set -DnewVersion=1.1-SNAPSHOT
Great and much simpler than I expected ;-)
Thanks (to both of you)
Jan
--
From address is
Wendy Smoak wrote:
If you find you need to make a fix, then you can branch from the tag
-- in your case the version number on your branch might be
1.5.1-SNAPSHOT.
How do I create a branch from a tag?
I have a:
2.0-SNAPSHOT (current /trunk/)
1.0 /tags/1.0/
and I want to have a
On Fri, Apr 30, 2010 at 10:07 AM, Jan Torben Heuer
jan_key67...@jtheuer.de wrote:
How do I create a branch from a tag?
I have a:
2.0-SNAPSHOT (current /trunk/)
1.0 /tags/1.0/
and I want to have a /branch/1.1-SNAPSHOT.
It is a a multi module project so version numbers must be changed.
I
If you are not using the release:perform, how are you creating the
releaser artifact 1.5 ? I am guessing you are running the install or
deploy from the new tag 1.5.
As far rescue changes, you will have to make changes to trunk or tag
and then merge them to the other.
Ideally I would create
If you're not using release:perform and you aren't pushing a blessed
jar anywhere (i.e. nexus), then you could just mvn release:rollback
(it might not be rollback, but there is some command that rolls things
back). Then, make your fixes and do release:prepare again.
I will add that the whole
On Wed, Apr 28, 2010 at 10:23 AM, napple fabble jm.postili...@gmail.com wrote:
The only thing I need to do is mvn release:prepare. This creates the
correct tag and updates trunk as I want it to. I haven't had any need for
release:perform.
Really? Where are you getting the released artifacts
2 separate and distinct versions to be simultaneous merged with an artifact
dependency may cause integration havoc later on..e.g.
trunk-1.5 merged with dependency-artifactV1.5
trunk-1.6 merged with dependency-artifactV1.6
best to use point release .1 .2 as wes mentioned trunk1.5 merges with
