Hi, > I guess one has to create a branch from the tagged version. Then the version >in the poms have to be set to 1.1.1-SNAPSHOT and then development starts.
Also don't forget to update the scm section of your pom. Your description of the process is good, but I don't know if there is a fully automated way (there is release:branch but AFAIK this is to create a branch from trunk, not a branch from tag). > And how about releasing it ? Can I use the release plugin again ? does it >understand that in the scm tag there is now "branches/xxx" instead of "trunk" >? Yes, release plugin works fine. Regards, Julien ----- Message d'origine ---- > De : "mremerson...@aim.com" <mremerson...@aim.com> > À : users@maven.apache.org > Envoyé le : Jeu 13 janvier 2011, 13h 42min 01s > Objet : how to patch releases > > > > > Hi all, > > this might be a simple one and if there is documentation about it I'm happy > to >read that. > > Its a basic understanding question: > > I have a maven project and do a release - lets say 1.1 > > The maven release plugin manipulates the poms and tags the software in the >scm. > > the trunk itself has e.g. 1.2-SNAPSHOT - everything is fine and the release > is >done > > > How is the procedure if one needs to patch 1.1 to 1.1.1 ? > > I guess one has to create a branch from the tagged version. Then the version >in the poms have to be set to 1.1.1-SNAPSHOT and then development starts. > > Is this process only doable by hand or is there also maven tools for that ? > > And how about releasing it ? Can I use the release plugin again ? does it >understand that in the scm tag there is now "branches/xxx" instead of "trunk" >? > > is it the same procedure ? > > Thanks for any clarification or any link > Emerson > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
