Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Action item: use of the jakarta groupId
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:


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:



_______________________________________________
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

Back to the top