Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove work-around for JAX-RS 1.x wrt JAX-RS 2 type NoContentException #134

Closed
cowtowncoder opened this issue Jan 20, 2021 · 2 comments
Closed

Remove work-around for JAX-RS 1.x wrt JAX-RS 2 type NoContentException #134

cowtowncoder opened this issue Jan 20, 2021 · 2 comments
Milestone
2.13.0

Comments

@cowtowncoder
Copy link
Member

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.
@cowtowncoder cowtowncoder added this to the 2.13.0 milestone Jan 20, 2021
@jihoonson jihoonson mentioned this issue Apr 7, 2022
Closed
2 tasks
pjfanning added a commit to pjfanning/jersey-1.x that referenced this issue Jul 11, 2022
@pjfanning
downgrade jackson due to FasterXML/jackson-jaxrs-providers#134
2a00b6f
@pjfanning
Copy link
Member

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)

@pjfanning pjfanning mentioned this issue Jul 11, 2022
Open
@cowtowncoder
Copy link
Member Author

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.

@wakingrufus wakingrufus mentioned this issue Oct 12, 2022
Closed
@abhishekagarwal87 abhishekagarwal87 mentioned this issue Aug 8, 2023
Merged
@janjwerner-confluent janjwerner-confluent mentioned this issue Dec 8, 2023
Closed
@jeremykwiatkowski jeremykwiatkowski mentioned this issue Dec 11, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.13.0
Development

No branches or pull requests
2 participants
@cowtowncoder @pjfanning