You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2023. It is now read-only.
I guess supporting jaxrs 2.0 api (and hence jersey 2.x) may easily imply breaking backward compatibility. Nevertheless I think it should be done in one way or another.
More specifically, at https://jersey.java.net/documentation/latest/modules-and-dependencies.html I've seen that a web application declaring jersey/jaxrs as dependencies should use the artifact jersey-container-servlet-core if the servlet container implements Servlet API older than 3.0, otherwise jersey-container-servlet. If the webapp is deployed within an application server providing jersey and jaxrs on its own, the dependency should be declared as provided.
We should find a way to provide the needed deps remaining servlet-api version independent.
From @srmelody on June 27, 2013 22:5
Jersey 2.0 is out:
https://jersey.java.net/
It would be great for this plugin to support the 2.0 version of Jersey.
Copied from original issue: krasserm#19
The text was updated successfully, but these errors were encountered: