Hi Wim
For testing, I tried to "release" the cwt bundles and features in
eclipse ide with version tiger plugin.
To be able to update also the parent pom (cwt/pom.xml) I imported
this into eclipse as project.
Then I defined "Release" as "Version operation" in the version
tiger dialog and pressed "Finish".
The changes made by version tiger look good to me:
It removed the "-SNAPSHOT" in the manifest.mf and pom.xml as well
as feature.xml and category.xml
Thus, I assume version tiger would work for nebula if you import
the parent (e.g cwt) projects into eclipse, or when you use
version tiger command line tool (very useful for repetetive tasks
like release, snapshot or increment bugfix version etc. We use it
when we automatically release tycho builds within jenkins).
Maybe, you can remove the version dependencies from the plugins to
the parent pom but use version tiger to keep these version equal.
>would it also know plugins and the connection between
MANIFEST.MF and pom.xml
Yes. That is one of the very good reason we use it: keep the
version in sync. (manifest.mf, plugin.xml, category.xml, feature.xml,
updatesite.xml...)
Our "version tiger specialist" is currently out of office. I will
ask him for a solution/thoughts regarding the parent pom version
dependency
Cheers Jan
--
Jan Hänsli
Inventage AG | CH-8005 Zürich | www.inventage.com
On 26/10/17 12:12, Wim Jongman wrote:
Hi Jan,
Unfortunately this does not work for the Nebula repository.
We have the widget version in the parent directory which the
tool does not recognize. If it would, would it also know
plugins and the connection between MANIFEST.MF and pom.xml?
Cheers,
Wim
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev
