Re: [ee4j-pmc] JAX-RS 2.1.2 @ Jakarta

["Markus KARG" <markus@xxxxxxxxxxxxxxx>]

Yes and no. For the published JAR it plays no role anyways, as these are "provided" dependencies, so simply nothing happens at runtime. Also, these dependencies do not yet exist on Maven Central, so it is inherently impossible to even *build* JAX-RS if we change to jakarta dependencies right now. Certainly we will as soon as that dependencies do exist.

-Markus

 

From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of lukas.jungmann@xxxxxxxxxx
Sent: Montag, 8. Oktober 2018 19:41
To: EE4J PMC Discussions
Subject: Re: [ee4j-pmc] JAX-RS 2.1.2 @ Jakarta

 

Hi,

 

   I see it has dependencies on 'javax' artifacts. Wasn't one of the goals of groupid change to also replace existing dependencies from 'javax' to 'jakarta' ones? Just asking as if not, it could probably simplify a lot of things...

 

 

Thank you,

--lukas

 

Sent from mobile

 

-------- Původní zpráva --------

Od: Markus KARG <markus@xxxxxxxxxxxxxxx>

Datum: 08.10.18 18:06 (GMT+01:00)

Komu: 'EE4J PMC Discussions' <ee4j-pmc@xxxxxxxxxxx>

Předmět: [ee4j-pmc] JAX-RS 2.1.2 @ Jakarta

 

FYI

 

In case you didn't notice, JAX-RS 2.1.2 is available on Maven Central using jakarts.ws.rs groupID since Sunday night. :-)

 

Thanks to the EF admins and the Sonatype admins I was able to re-release.

 

Note that Sonatype needs to know the relation between the new groupIDs and user accounts to both stages, staging and releasing, which was not given for JAX-RS so far (they fixed it on the weekwend). So maybe it is a good thing to double-check with Sonatype before other projects get stuck while releasing.

 

-Markus