[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-pmc] Action item: use of the jakarta groupId
|
My arguments assumed that it has to be done and that we just have to decide whether to do it now or later.
So far I did not hear any valid legal nor technical reason.
-Markus
It will be "marketing" stufd whenever we do it, but it's less disruptive and understandable now than between releases.
As a user, I can assume "javax" was changed to "jakarta" as part of the transition process. But if that changes months later, that gives me a strange message of instability, even if it has no technical downsides.
That is no big change. For application programmers this simply is marketing stuff, hence no reason at all.
To: EE4J PMC Discussions
Subject: Re: [ee4j-pmc] Action item: use of the jakarta groupId
The "big change" now is the transition from Java EE to Jakarta EE. For me, that justifies that name change now more than for the next version.
-1 for re-releasing or immediate change
+1 for jakarta namespace starting with Jakarta EE 9
For EE 9 JAX-RS will have a major version bump anyways due to incompatible changes. So users accept such a change easily. From Java EE 8 to Jakarte EE 8 the version was just bumped from 2.1 to 2.1.1. So a change of the groupId right now look ridiculous to users.
-Markus
Subject: Re: [ee4j-pmc] Action item: use of the jakarta groupId
Dmitry,
Not sure if you had a chance to review the doc that David references, but there is good justification for doing this maven coordinate change now rather than later... It will be very clear that these Eclipse-based artifacts are part of the Jakarta EE effort. And, this adds to the good story that we're putting together for the fall conferences.
Since JAX-RS is the only project that has released something new, the relative hit should be containable. The other EE4J projects should be able to modify their release artifacts to use this new jakarta group and artifact id convention. This would be less work than allowing everyone to go forward with the javax maven coordinate now and then ask them to do yet-another-release immediately after with the jakarta maven coordinates. Wouldn't it?
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
From: Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx>
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Date: 09/12/2018 02:09 PM
Subject: Re: [ee4j-pmc] Action item: use of the jakarta groupId
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
This is extra work to do. The release schedule is tough enough without this extra task. We can do it for the next Jakarta EE release. I see no sense doing it now. I am voting -1.
— Dmitry
On 12 Sep 2018, at 20:20, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
Following up from the specification committee meeting. We (PMC) need to make sure all the specifications/api jars we release to Maven Central are in the jakarta groupId. Using JMS as an example:
- https://github.com/eclipse-ee4j/jms-api/commit/8c6519d5544b49fa3fed672182d222f6c874aa54
If you want an easy command to do it:
$ perl -i -pe 's,Id>javax,Id>jakarta,g' pom.xml
We'll need to re-release JAX-RS and make sure we add this to our spreadsheet to track which projects have done it.
Here's the document for reference with motivations on the change in Maven coordinates:
- https://docs.google.com/document/d/1pm8fjNusxxecoI-9M-eYvnoTkmZTMraQETN7OeVyMnA/edit#heading=h.ma7xbsxflh33
--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc