Thanks for your advice. I fixed it manually!
On Fri, Feb 17, 2012 at 9:04 PM, Tommaso Teofili <[email protected]> wrote: > 2012/2/17 Edward J. Yoon <[email protected]> > >> Oh..... it seems automatically committed by "mvn release:prepare" command. >> > > yes, that's fine since the mvn release:prepare automatically updates > versions on trunk. > Also that command should create the SVN tag automatically while it seems > it's just been svn copied from trunk to tag. > > >> Should I re-create RC? or Changing svn directly is OK? >> > > I think that for the purpose of this release we can just manually change > poms but for the future ones it'd be better to fix the process ;) > > Tommaso > > > >> >> On Fri, Feb 17, 2012 at 8:33 PM, Tommaso Teofili >> <[email protected]> wrote: >> > Hi all, >> > >> > one thing I found strange is that the SVN tag pom.xml files have been >> > updated to 0.4.1-incubating-SNAPSHOT. >> > As far as I know the SVN tag should contain a 0.4.0-incubating version >> > while the trunk should instead contain the 0.4.1-incubating-SNAPSHOT >> > version. >> > >> > @Edward: did you use the maven-release-plugin to create the tag? >> > >> > Regards, >> > Tommaso >> >> >> >> -- >> Best Regards, Edward J. Yoon >> @eddieyoon >> -- Best Regards, Edward J. Yoon @eddieyoon
