|
Mickael, Thanks a lot for the time to taken to explain me those elements. I will try at least to setup the Tycho compare version for the papyrus project,
https://git.eclipse.org/r/#/c/98880/ I will explore the links you provided. Have a good day. Francois De : tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
De la part de Mickael Istria Hi,
First, this is actually a good OSGi practice to *not* update versions unless needed (ie if resulting binary did chnage). Not changing version allows to have a broad compatibility range, which can be pretty convenient. PDE API Tools can
help (in the IDE) to remind to update versions according to OSGi best practices, at Tycho level, there isn't an easy way to enable PDE API Tools. However, if you're concerned about compatibility, you can use a combination of reproducible version quilifiers (
https://wiki.eclipse.org/Tycho/Reproducible_Version_Qualifiers#What_does_this_actually_do.3F ) and of
https://www.eclipse.org/tycho/sitedocs-extras/tycho-p2-extras-plugin/compare-version-with-baselines-mojo.html . That would mostly make your build fail is the content of the resulting jar actually changed (ie if there were code change mostly). Then, from
this failure, the developer gets reminded to update the version.
There might be existing mojos or you can write your own one that looks at all modules in the reactor and fail if they are not equals. But as far as I know, it's not a common practice.
No. -- Mickael Istria Eclipse IDE developer, at
Red Hat Developers community |
↧
Re: [tycho-user] way to check required-plugin version
↧