The getID/setID methods were migrated from Long to
The change was introduced by
Type of Entity-IDs (changed in api.base, api.default, api.ods)
Itâs quite recent. Three commits later the
repository was tagged with 0.7. 14 commits later it was tagged
with 0.8 (on September 7th). Yet the projectâs version is still
set to 1.0.0.
So which is it? Is it 0.8? is it 1.0.0? Arenât we
supposed to be using semantic versioning for labeling project
versions? If we are then the current state of the project is
horribly broken. This âsmall changeâ should have prompted the
project version to jump to 2.0.0-SNAPSHOT at the very least if
semver is to be followed to the letter. If weâre not following
semver, then what is it?
I ask then, what versioning scheme is in place and
where do we get hold of the document that states it?
The mdmbl website points to Eclipseâs bugzilla if you want to
report a bug or review bug reports.Âhttps://projects.eclipse.org/projects/technology.mdmbl/developer
You never ever, let me repeat that, NEVER EVER use
version ranges at any time, for whatever reason!
Their usage lead to unreproducible builds and
other potential incompatibility issues. Granted, Mockito is a
project that evolves very, very fast, they push releases at
least once a month, and as great as they try to keep things
tidy they broke binary compatibility by moving around private
APIs between 2.6.x and 2.7.0. This could happen again.
Matthias, youâre exposing the project and every developer that
wants to build the project to potential problems just because
you couldnât be bothered to pick a fix version for a
dependency. If you didnât pick the version range at least you
signed of the commit. Please do not do this. This problem
should have been spotted in a code review.