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

Pleas stay compatible with Maven best practices. In particular, build
numbers must not have letters in Maven versions because they would break the
version range feature.
-Markus

-----Urspr√ľngliche Nachricht-----
Von: jakartaee-platform-dev-bounces@xxxxxxxxxxx
[mailto:jakartaee-platform-dev-bounces@xxxxxxxxxxx] Im Auftrag von Bill
Shannon
Gesendet: Mittwoch, 15. Januar 2020 22:30
An: jakartaee-platform developer discussions
Betreff: [jakartaee-platform-dev] version numbers and release qualifiers

I've updated our versioning spec [1] to reflect our recent decision to
use dot-dot version numbers for API jar files, e.g., of the form x.0.0.
Please let me know if you see any mistakes, especially in the OSGi rules.

Also, we need to decide what release qualifiers to recommend.  So far
we've been recommending these (where <number> is a sequence number):

-b<number>	- build
-m<number>	- milestone
-rc<number>	- release candidate

The pre-defined qualifier is "-SNAPSHOT", which raises the question as
to whether our qualifiers should be upper case as well.  I've mostly
seen lower case being used, which is why the document recommends lower
case, but I can see an argument for all qualifiers being upper case.

Comments?

Once we come to a decision on this I'd like to send it to the PMC and
ask them to "bless" it as the recommendation for all EE4J and Jakarta EE
projects.

Thanks.


[1] https://wiki.eclipse.org/JakartaEE_Maven_Versioning_Rules
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev



Back to the top