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: [email protected] > To: [email protected] > > 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 <[email protected]> > 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > _________________________________________________________________ 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
