-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Jersey 2.0 #19
Comments
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. |
+1 (though, Grails itself provides many of the same things that Jersey v2.0 provides over the v1.x line) |
This issue was moved to budjb#2 |
Jersey 2.0 is out:
https://jersey.java.net/
It would be great for this plugin to support the 2.0 version of Jersey.
The text was updated successfully, but these errors were encountered: