[jbosstools-dev] Problem with component version on branch 4.1.x
Xavier Coulon
xcoulon at redhat.com
Thu Sep 5 04:13:21 EDT 2013
Hello,
[Just sharing the story that happened to me this morning]
While talking with Max, Rob and André, we realized that the current Livereload version on branch 4.1.x was '1.1.0-SNAPSHOT' while it should have been '1.0.1-SNAPSHOT'. The reason for this is that I applied the same version bump on 'master' and 'jbosstools-4.1.x' branches. This means that both branches were running the same version. Which is wrong :-/
Pushing down the version from 1.1.0 to 1.0.1 on branch 4.1.x was not an option, so we decided that the best solution was to stick to 1.1.0-SNAPSHOT on the 4.1.x branch and bump master to 1.2.0-SNAPSHOT.
Max wrote a blog article in which he shared the magic mvn command to run to make the version bump is all pom.xml, feature.xml and MANIFEST.MF files at once. In my case, I just ran:
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT
(and then mvn clean verify)
So this should keep things clear in the sense that versions of the Livereload component in JBT 4.1.1 and in JBT 4.2.0 won't be the same, even though they don't follow the initial plan :-/
Best regards,
/Xavier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20130905/af3996b6/attachment.html
More information about the jbosstools-dev
mailing list