-
Notifications
You must be signed in to change notification settings - Fork 80
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
Remove work-around for JAX-RS 1.x wrt JAX-RS 2 type NoContentException
#134
Milestone
Comments
fyi - this causes issues for projects using jersey-core v1 and/or jsr311-api jar (Hadoop eco-system, for instance) - these are old and I'm not requesting for this change to be undone - the workaround is to use Jackson 2.12.6.1 or 2.12.7 (if you want CVE free jackson) |
Thank you @pjfanning this is good to know. Might also mean that 2.12.x branch needs to be kept open bit longer than it otherwise would. |
This was referenced Jul 25, 2024
cowtowncoder
pushed a commit
that referenced
this issue
Jul 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like there is still a work-around to not require JAX-RS 2.x exception type
NoContentException
in codebase.That seems unnecessary as dependency to JAX-RS 2.0 has been around for years now, so let's remove this kludge.
The text was updated successfully, but these errors were encountered: