jakarta.ws.rs:all:4.0.0-M2 missing in Maven Central

[jskillin-idt]

jakarta.ws.rs:all:4.0.0-M2 missing in Maven Central

[jamezp]

Hello @jskillin-idt. We are trying to sort out the issue of being able to release 4.0.0. The 4.0.0-M2 on Maven central unfortunately is not correct. The current release is 3.1.0 with 4.0.0 coming out very soon. Hopefully before the end of the week.

One thing to note is 4.0.0 is a new API and there may be a lag in a final release of implementations.

[jamezp]

Yeah, hopefully a release will be out soon. With Maven Central you can't really remove or replace archives. It's probably best to work off SNAPSHOTS of main for now if you're trying to implement the API.

[jskillin-idt]

Unfortunately, my situation far more mundane than trying to implement the latest API. 😄 I am using dynamic version ranges in Gradle, and 4.0.0-M2 happened to be selected as the upper end of that range, which caused Gradle to try to parse the metadata of 4.0.0-M2, which then triggered a failure when certain POMs didn't exist as needed to complete resolution.

The issue is simple enough to work around until the latest version on Maven Central changes. I appreciate you taking the time to reply to my comments.

[senivam]

fix for the described issue is on the infrastructure (Jenkins job). Advice on the fix is described in the #1253

[jskillin-idt]

There is probably no purpose, then, in removing or fixing the 4.0.0-M2 release in Maven Central? I'll work on a way for my build to ignore the 4.0.0-M2 as an exception, if the plan is just to let the 4.0.0-M2 remain published as is and let a future release supersede.

[jamezp]

Given that I will close this. If for some reason you feel this needs to be reopened please feel free to reopen it.

I will say, once 4.0.0 is out you'd need to change your implementation. The new API will have methods not implemented in currently released RESTEasy, Jersey, etc.