So, with Javax->Jakarta developments wherein JAXB api is now forked hard, we have an attempted workaround of using classifier "jakarta", publishing 2 jar variants.
But this seems to have issues at least wrt OSGi; so maybe we better bite the bullet, create 2nd module with copied code but covering Jakarta variant of XML binding API.
Also see my question on what to call "new" JAXB:
jakartaee/jaxb-api#179
This would be for Jackson 2.13. Trade-off as I see it:
- CON: More code to maintain for now -- possibly not for 3.0 (if we only migrate new variant)
- PRO: Known to work: 2 different artifacts, simple dependencies, no post-processing