[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakarta.ee-community] version numbers and release qualifiers
|
I don't really use Twitter, but if you or someone else could do this
and give us the answer, that would be helpful.
Thanks!
Edwin Derks wrote on 1/27/20 11:07 PM:
Hi all,
I have been following this thread But I also
don’t have the answers. May I suggest that you send a Twitter
PM to Robert Scholte (Maven Chair), asking support for our
questions? I’m pretty sure that he has the answers and
represents the Maven community. And as far as I know him, he
is more than willing to help.
Hope this helps.
Edwin
It's
is as simple as you do it here: They have mailing
lists. They uses votings.
-Markus
Von:
Bill Shannon [mailto:bill.shannon@xxxxxxxxxx]
Gesendet:
Montag, 27. Januar 2020 23:57
An:
Jakarta EE community discussions; Markus KARG
Betreff:
Re: [jakarta.ee-community] version numbers and
release qualifiers
I don't
know how to ask the entire Maven community. If you
do, please do so and report the results.
Markus KARG wrote on 1/27/20 2:52
PM:
There
is a simple answer to find out the Maven
community's will: Ask them.
-Markus
If you're saying it's merely
for the naming convention of Maven plugins but not
any other artifacts, I guess that means it is not
really representative or relevant outside that
context ;-)
And even there it is far from
being applied nowadays, the most popular
examples are Surefire
I
think the question is, what does the Maven
community themselves,
not what do others at Apache.
-Markus
Because it's not even
done by most Apache projects like TomEE
Tomcat
and even Apache
Archiva related to Maven itself
None of them use
lowercase. The only exception seems to
be the "incubating" postfix or
qualifier, but that doesn't even
compare to those mentioned here,
because there isn't any identical
version number without the
"incubating" string, so it's something
very Apache Foundation specific.
If Maven's Best
Practice is to use lower case, then I do
not see why we
should got with upper case instead.
SNAPSHOT is a special case as it is not
a static qualifier but actually a
trigger for a dynamic search ("find
latest").
-Markus
-----Ursprüngliche Nachricht-----
Von: jakarta.ee-community-bounces@xxxxxxxxxxx
[mailto:jakarta.ee-community-bounces@xxxxxxxxxxx]
Im Auftrag von Bill
Shannon
Gesendet: Montag, 27. Januar 2020 22:33
An: Jakara EE community discussions
Betreff: [jakarta.ee-community] version
numbers and release qualifiers
As most of you know, our rules for use
of version numbers is published here:
https://wiki.eclipse.org/JakartaEE_Maven_Versioning_Rules
I wanted to highlight recent decisions
and validate one of them with this
group.
After a discussion in the platform
project team, I've updated the rules to
reflect a decision we made:
All Maven programming artifacts (read:
jar files containing class files)
are versioned with a three component
version number
<major>.<minor>.<micro>.
In particular, API jar files use this
three component version number, not
the two component number used by
specifications.
While, in usual fashion, this is only a
recommendation for project teams,
we consider this to be a very *strong*
recommendation.
Another issue we decided, but that I
haven't updated the document to
reflect,
is that version qualifiers should always
be upper case. Version qualifiers
follow the version number with a dash.
For example, in the version
1.2.3-SNAPSHOT, "SNAPSHOT" is the
qualifier.
The other common qualifiers in use are:
M - milestone
RC - release candidate
B - build, or sometimes beta
These qualifiers are followed by a
number, allowing for multiple, ordered,
milestones or release candidates or
builds/betas. This results in versions
such as: 1.2.3-M1, 4.5.6-RC2, 7.8.9-B37,
etc.
The Maven rules for ordering of versions
are here:
https://maven.apache.org/pom.html#Version_Order_Specification
You'll notice that the Maven rules use
lower case for the qualifiers
even though Maven ignores case when
comparing qualifiers, and SNAPSHOT is
effectively always used in upper case.
While there was a strong consensus in
the platform project team that version
qualifiers should always be lower case,
I wanted to check with the larger
community to make sure we're not going
against some wider community or Maven
or other convention with the use of
upper case.
If you have any concern about the use of
upper case, and especially if you
can
point to evidence of lower case being a
stronger convention, please let me
know.
Silence means you agree upper case is
best and thus there's no need to
reply.
Thanks.
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options,
retrieve your password, or unsubscribe
from
this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options,
retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-community