jackson-module-jakarta-xmlbind-annotations should use a Jakarta namespaced Activation API
#175
Milestone
Comments
This was referenced May 24, 2022
|
Ugh. Apologies for the mess here. It does sound like something we'd want for 2.13 too. I'll add a note on PR. |
cowtowncoder
changed the title
jackson-module-jakarta-xmlbind-annotations should use a Jakarta namespaced Activation API
cowtowncoder
added a commit
that referenced
this issue
May 25, 2022
#175: Migrate to a Jakarta namespaced activation API.
cowtowncoder
added a commit
that referenced
this issue
May 25, 2022
|
Excellent. Thanks for the quick turnaround on this! Should this be closed now since #177 is merged? |
|
Yes, forgot to close. Fixed for |
|
@cowtowncoder Is there by chance a 2.13 or 2.14 release coming soon? I'd just like to integrate this into RESTEasy and WildFly. |
|
Probably not quite around the corner: hoping to finalize 2.14 soon but it'll take a while. |
|
No worries. Thanks for the update! |
This was referenced Aug 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the
com.fasterxml.jackson.module:jackson-module-jakarta-xmlbind-annotationsuses usesjakarta.activation:jakarta.activation-api:1.2.2. This is ajavaxnamespaced API. The version 2.0.1 should be used to align withjakarta.xml.bind:jakarta.xml.bind-api:3.0.1.If this can also be backported to 2.13 please let me know as this is a blocker for RESTEasy and WildFly to be able to upgrade.
The text was updated successfully, but these errors were encountered: