JEP 223: New Version-String Scheme
Remi Forax
forax at univ-mlv.fr
Wed Nov 5 07:53:23 UTC 2014
On 11/04/2014 11:05 PM, mark.reinhold at oracle.com wrote:
> New JEP Candidate: http://openjdk.java.net/jeps/223
>
> - Mark
Hi Mark,
I fail to see why dropping the first 1 is interesting.
While it's true than $MAJOR will be always '1', and that each release
slightly violating the principle of semantic versioning, it see that
more like the difference between a principle and the reality than
something that has to be fixed.
IMO, having a difference between the marketing name and the engineering
version value doesn't worth the trouble of the compatibility issues you
list.
Why not stick with a 4 components version ?
And for the API, version() should be versions() and return an int[] and
build() should return an OptionalInt.
cheers,
Rémi
More information about the platform-jep-discuss
mailing list