Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] version numbers and release qualifiers

EDR was used by the JCP for its Early Draft stage, see, similar for Public Review, Proposed Final Draft and in some cases maybe also Maintenance Releases.


The Jakarta EE qualifier for Drafts would only be something like



In fact some, mostly Oracle led JSRs already applied that kind of pattern earlier and the EDR of a particular Java EE spec might have been 2.0.0-bXY or similar.





From: Piotr Żygieło
Sent: Tuesday, January 21, 2020 19:33
To: jakartaee-platform developer discussions
Subject: Re: [jakartaee-platform-dev] version numbers and release qualifiers


On Tue, 21 Jan 2020 at 18:12, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:


> Do I really have to run the program for you guys?  :-)  You can run this yourself:


> $ java -jar maven/lib/maven-artifact-3.3.3.jar 2.0-EDR 2.0

> Display parameters as parsed by Maven (in canonical form) and comparison result:

> 1. 2.0-EDR == 2-edr

>    2.0-EDR > 2.0

> 2. 2.0 == 2


> You are not "good".  :-(


> I think the problem is that "EDR" is not one of the builtin qualifiers that Maven knows about.  It appears that only builtin qualifiers are "less than" the release.  (And yes, I got this wrong at first by making assumptions without running the program.)



I don't see EDR in discussed


The only non-number component is "b" in "Version numbers for non-final

specifications" section I think.

Why it would matter then?






jakartaee-platform-dev mailing list


To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top