You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by napple fabble <jm...@gmail.com> on 2010/04/28 16:23:56 UTC
Release plugin and updating a release with some fixes
I use release plugin to update my pom.xml and create tags in subversion.
I just created a new release with it. While development was ongoing, my
pom.xmls had version 1.5-SNAPSHOT. Release plugin created tag "1.5" and
updated my trunk to 1.6-SNAPSHOT. So everything is as I want.
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.
QUESTION: What do I do when I find some last bugs while installing the
release and want to fix them. I would ideally like to have both 1.5 tag and
the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow
conveniently with release plugin, or do I have to do it manually (if so,
what's the best approach? just fix trunk and copy the changed to the tag?).
--
View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.html
Sent from the maven users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Release plugin and updating a release with some fixes
Posted by Martin Gainty <mg...@hotmail.com>.
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 dependency 1.5 =>1.5.1
and then promote from that point..
otherwise you'll have to 'manage' (branch..merge..and run integrations tests) 2 separate trees
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Wed, 28 Apr 2010 11:13:31 -0400
> Subject: Re: Release plugin and updating a release with some fixes
> From: wesw@wantii.com
> To: users@maven.apache.org
>
> 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 thing sounds a bit hackish and you should
> get an MRM. Then, if you find bugs, you can make a branch based on the
> 1.5 tag, fix your bugs, then merge the changes back to trunk. You can
> also release from the branch and name it 1.5.1 (or similar).
>
> -Wes
>
> On Wed, Apr 28, 2010 at 10:23 AM, napple fabble <jm...@gmail.com> wrote:
> >
> > I use release plugin to update my pom.xml and create tags in subversion.
> >
> > I just created a new release with it. While development was ongoing, my
> > pom.xmls had version 1.5-SNAPSHOT. Release plugin created tag "1.5" and
> > updated my trunk to 1.6-SNAPSHOT. So everything is as I want.
> >
> > 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.
> >
> > QUESTION: What do I do when I find some last bugs while installing the
> > release and want to fix them. I would ideally like to have both 1.5 tag and
> > the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow
> > conveniently with release plugin, or do I have to do it manually (if so,
> > what's the best approach? just fix trunk and copy the changed to the tag?).
> > --
> > View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.html
> > Sent from the maven users mailing list archive at Nabble.com.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
>
> --
> Wes Wannemacher
>
> Head Engineer, WanTii, Inc.
> Need Training? Struts, Spring, Maven, Tomcat...
> Ask me for a quote!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5
Re: Release plugin and updating a release with some fixes
Posted by Wes Wannemacher <we...@wantii.com>.
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 thing sounds a bit hackish and you should
get an MRM. Then, if you find bugs, you can make a branch based on the
1.5 tag, fix your bugs, then merge the changes back to trunk. You can
also release from the branch and name it 1.5.1 (or similar).
-Wes
On Wed, Apr 28, 2010 at 10:23 AM, napple fabble <jm...@gmail.com> wrote:
>
> I use release plugin to update my pom.xml and create tags in subversion.
>
> I just created a new release with it. While development was ongoing, my
> pom.xmls had version 1.5-SNAPSHOT. Release plugin created tag "1.5" and
> updated my trunk to 1.6-SNAPSHOT. So everything is as I want.
>
> 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.
>
> QUESTION: What do I do when I find some last bugs while installing the
> release and want to fix them. I would ideally like to have both 1.5 tag and
> the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow
> conveniently with release plugin, or do I have to do it manually (if so,
> what's the best approach? just fix trunk and copy the changed to the tag?).
> --
> View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.html
> Sent from the maven users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Wes Wannemacher
Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin and updating a release with some fixes
Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Apr 30, 2010 at 10:07 AM, Jan Torben Heuer
<ja...@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 think either the release or scm plugin has a "branch" goal. I
usually just do the copy
svn cp http://url/of/tag http://url/of/new/branch
and then update the version numbers later. (The versions plugin can
help, as Tim mentioned.)
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin and updating a release with some fixes
Posted by Stephen Connolly <st...@gmail.com>.
Don't forget to update the scm section in the pom.xml files
On 5 May 2010 08:38, Jan Torben Heuer <ja...@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 valid until 01.06.2010
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Release plugin and updating a release with some fixes
Posted by Jan Torben Heuer <ja...@jtheuer.de>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin and updating a release with some fixes
Posted by Tim O'Brien <to...@discursive.com>.
mvn versions:set -DnewVersion=1.1-SNAPSHOT
On Fri, Apr 30, 2010 at 9:07 AM, Jan Torben Heuer
<ja...@jtheuer.de> wrote:
> 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 /branch/1.1-SNAPSHOT.
> It is a a multi module project so version numbers must be changed.
>
> Jan
> --
> From address is valid until 01.06.2010
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin and updating a release with some fixes
Posted by Jan Torben Heuer <ja...@jtheuer.de>.
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 /branch/1.1-SNAPSHOT.
It is a a multi module project so version numbers must be changed.
Jan
--
>From address is valid until 01.06.2010
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin and updating a release with some fixes
Posted by napple fabble <jm...@gmail.com>.
Sorry, could not respond to this thread sooner...
Wendy Smoak wrote:
>
> On Wed, Apr 28, 2010 at 10:23 AM, napple fabble <jm...@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 then? Release
> Perform is what checks out from the newly created tag and builds the
> artifacts...
>
>
What I do is just
1. release:prepare
2. go to tags/<release_version>
3. build there
4. copy the created artifacts (such as a jar) to production
I don't have any need for deploying the artifacts to any repositories other
than my local one.
Step 4 is actually automatic, there's a maven antrun plugin bound to
install-phase which scp's the created artifact to the correct phase. There
might be some more "maven-like" alternative for doing this, but I rememer
trying out a few things when I was setting up the build and this way I at
least got it working.
I would like the while process to be as straightforward as possible and as
little direct svn branching / merging as possible. I think I will just do
like
1. create release 1.5 with release plugin
2. if I find out something to fix, fix it
3. create release 1.5.1 with release plugin
For some reason I was assuming that if I have used release plugin to release
1.5 and make current version 1.6-SNAPSHOT I would not be able to "go back"
and release 1.5.1....but I guess that would not make much sense. I will try
that.
--
View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p5012967.html
Sent from the maven users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin and updating a release with some fixes
Posted by Wendy Smoak <ws...@gmail.com>.
On Wed, Apr 28, 2010 at 10:23 AM, napple fabble <jm...@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 then? Release
Perform is what checks out from the newly created tag and builds the
artifacts...
> QUESTION: What do I do when I find some last bugs while installing the
> release and want to fix them. I would ideally like to have both 1.5 tag and
> the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow
> conveniently with release plugin, or do I have to do it manually (if so,
> what's the best approach? just fix trunk and copy the changed to the tag?).
What scm tool are you using? The following assumes Subversion:
Generally tags are not changed, the point is to know exactly what code
your release came from.
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.
Then you would merge the fix from the branch to your 1.6-SNAPSHOT trunk.
At that point you can release one or both with the fix. But version
1.5 should not be "updated" with the fix -- it's already released.
Just move on to 1.5.1. Version numbers are free. :)
If you really, really want "Version 1.5" to be perfect, then consider
releasing some alpha/beta/milestone/release candidates beforehand.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Release plugin and updating a release with some fixes
Posted by Kumar Ampani <am...@gmail.com>.
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 another release 1.5.1 using release;prepare and
perform which will create a tag for 1.5.1 as well so that you will
have reproducable builds for both 1.5 and 1.5.1
On 4/28/10, napple fabble <jm...@gmail.com> wrote:
>
> I use release plugin to update my pom.xml and create tags in subversion.
>
> I just created a new release with it. While development was ongoing, my
> pom.xmls had version 1.5-SNAPSHOT. Release plugin created tag "1.5" and
> updated my trunk to 1.6-SNAPSHOT. So everything is as I want.
>
> 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.
>
> QUESTION: What do I do when I find some last bugs while installing the
> release and want to fix them. I would ideally like to have both 1.5 tag and
> the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow
> conveniently with release plugin, or do I have to do it manually (if so,
> what's the best approach? just fix trunk and copy the changed to the tag?).
> --
> View this message in context:
> http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.html
> Sent from the maven users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Sent from my mobile device
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org