7:52 p.m.
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
12:05 a.m.
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
3:20 a.m.
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?
Not going that far yet - but that is what everyone else is doing for releases in JBoss.
I'd argue that this is only useful once a year
This is not true and and assumption I want to change.
You bump your versions at every release - and for a stream that until now have meant
bumping it 2 to 3 times a year.
Once we go to having a proper/real release train out for supporting SOA tooling split -
this becomes even more important;
relying on a timestamp difference is simply not acceptable/enough.
, 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,
This is what this allow - each module that actually does changes bump their
plugins/features.
Until now we have worked with the rule: Change what actually changes - but I can tell you
now after having
gone through every plugin *very few* of the plugins and features have actually been
versioned properly.
Thus if the svn history speaks truly - many features and some features haven't been
bumped a single digit for years
even though they had plenty of changes.
The qualifier at the same time saved us but also hides the problem.
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 targeted).
I did not say to remove the qualifier.
I would love we eventually could use the API generated qualifiers instead of timestamp
though - but I know that
won't happen before tycho supports that notion.
/max
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
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
4667
days inactive
4667
days old
jbosstools-dev@lists.jboss.org
2 comments
2 participants
participants (2)
-
Max Rydahl Andersen -
Nick Boldt