Hi,
> On 20 Sep 2019, at 11:23, Robert Munteanu <[email protected]> wrote: > > 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. Which bundle are we talking about? Do you already have a branch with your changes? > > 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. Was there also an API change as part of the parent bundle update? If yes, then isn’t this aligned to what we discussed during the committer’s roundtable where we said it would be better to also update the bundle version if an API package provided by the bundle also gets a version bump? Thanks, Radu [0] - https://bnd.bndtools.org/chapters/170-versioning.html <https://bnd.bndtools.org/chapters/170-versioning.html>
