I'm not really a fan of tool telling us how to do bundle versions -
packages versions, yes. But bundle versions are marketing versions and I
doubt that a tool is always doing the right thing.
So regardless of the other discussions here, I rather would opt for a
switch to turn that part off.
Leaving SNAPSHOT aside, version ordering based on the qualifier is a
tricky thing and I would rather stay away from it in general. The
qualifier is compared by string comparision which makes "10" lower than
"2" and other "surprising" comparisions.
Therefore the odd/even policy solves handling the differences between
maven and OSGi versions and also keeps us away from surprises
Regards
Carsten
Am 20.09.2019 um 11:23 schrieb Robert Munteanu:
Hi,
After locally updating a module to use the latest parent pom, with the
bnd Maven tooling, I get a complaint with bnd that the version is too
low.
The bundle version change (1.2.6 to 1.2.7) is too low, the new version
must be at least 1.3.0
That is fine, and I agree with it. However, it goes against our
practice of using odd/even versioning numbers and changing the version
on release.
I've disabled the baseline check for that module for now, but it would
be good to have a more permanent solution.
Thanks,
Robert
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
