A huge thank you to Brain Fox and Sonatype for turning this around so quickly. Jakarta EE appreciates your support.
- https://issues.sonatype.org/browse/OSSRH-42639
The jakarta groupId in Maven Central is ready for us to claim. Now it's a full tilt race to see which spec community can get there first and go down in history as the first project to use it :)
Game on!
-- David Blevins 310-633-3852
+1. David's document sounds pretty reasonable and I think this is the right moment.
That said, this is pretty easy stuff that we (the community) should help with, providing PRs for all projects. New imported projects could directly use 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@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
|
