Bump jersey2-api from 2.38-1 to 2.39-1 in /bom-weekly

[dependabot]

Bumps jersey2-api from 2.38-1 to 2.39-1.

Release notes

Sourced from jersey2-api's releases.

2.39-1

🚦 Tests

• Improve test coverage (#58) @​basil

📦 Dependency updates

• Bump jersey-bom from 2.38 to 2.39 (#57) @​dependabot
• Bump javax-activation-api from 1.2.0-5 to 1.2.0-6 (#56) @​dependabot
• Bump plugin parent POM from 4.53 to 4.55 (#55, #50) @​dependabot
• Bump git-changelist-maven-extension from 1.4 to 1.6 (#54, #52) @​dependabot
• Bump jaxb from 2.3.7-1 to 2.3.8-1 (#53) @​dependabot
• Bump jackson2-api from 2.13.4.20221013-295.v8e29ea_354141 to 2.14.2-319.v37853346a_229 (#51) @​dependabot

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @jglick.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[jglick]

@dependabot squash and merge

[dependabot]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

[jglick]

Failure looks legitimate. Not familiar enough with the library to know what it means offhand.

[MarkEWaite]

jenkinsci/gitlab-plugin#1419 also reports an issue with the jersey2 api plugin 2.39-1 that was not visible with the jersey2 api plugin 2.38-1. I don't see anything to indicate that the failure in bom is directly related to the failure reported in the gitlab plugin, but both seem specific to the 2.39-1 release of jersey2 api.

[jglick]

This one FTR

RESTEASY003145: Unable to find a MessageBodyReader of content-type application/xml;charset=utf-8 and type class org.glassfish.jersey.JerseyTest$Employee

[MarkEWaite]

This one FTR

RESTEASY003145: Unable to find a MessageBodyReader of content-type application/xml;charset=utf-8 and type class org.glassfish.jersey.JerseyTest$Employee

I'm seeing a stack trace related to MessageBodyReader when I run the tests locally with:

PLUGINS=jersey2-api bash local-test.sh

I'll do some deeper study later today to better understand what changed between jersey2 2.38 and jersey2 2.39.

[MarkEWaite]

@dependabot close

Closing this pull request because there appears to be a breaking change in the Jersey 2.39 API from:

• Optional Injection-less client side for SE eclipse-ee4j/jersey#5232

That pull request removed the no-args constructor on the DefaultJacksonJaxbJsonProvider class and added a constructor with the @Inject annotation and two arguments. It appears that RESTEasy needs the old constructor rather than the new constructor.

There may be an expectation that a class with an internal in its package name is not used by outside consumers like RESTEasy, but that expectation does not match with the behavior expected by RESTEasy client 3.15.3 (released Mar 5, 2021) as used by the current release of the Jenkins GitLab plugin.

I'm not yet sure how to create a case that will show the problem clearly to the Jersey maintainers. I will continue to explore ways to show that to them.