So, you want to start having component owners use this right before GA
to drop the -SNAPSHOT qualifier, then right after GA to bump everything
up in one shot?
I'd argue that this is only useful once a year, when we start the new
year's release and need to push everything up from 3.6.x to
3.7.0-SNAPSHOT. Otherwise it's better to just upversion plugins and
features THAT ACTUALLY CHANGE, and that dropping the suffix is bad from
an osgi/p2 installable point of view (and also because you lose the M2
suffix so that QE knows for which milestone a given build is targetted).
On 07/28/2011 06:52 AM, Max Rydahl Andersen wrote:
Hi,
I've just committed the last bulk of changes to pom.xml, manifest.mf and feature.xml
to implement
https://issues.jboss.org/browse/JBIDE-9268
This change makes it so that almost all[1] modules in jboss tools svn can now be easily
versioned by using one command in the root of your module:
i.e. for cdi:
cd trunk/cdi
mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=3.4.0-SNAPSHOT
will correctly update all child pom's version info to 3.4.0-SNAPSHOT and any p2
metadata such as manifest.mf and feature.xml to 3.4.0.qualifier.
This means no need to manually bump each individual plugin on changes - it can now be
done at a module level.
Please be aware I have simply used the highest version found in the module to use as the
overall version - I have not checked if
that version is actually correct. That is up to each dev to check.
[1] There are some exceptions which ill cover in separate email.
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com