Ok, some bad news: for some (still poorly understood) problem, there
were issues in 2.12.2 release of following modules:
* JAX-RS providers (all)
* JSR-353 (old JSON-P) datatype
These modules had been changed to produce both "regular" variants to
refer to older J2EE APIs, and matching "-jakarta" (maven classifier
"jakarta") variants for newer Jakarta 2.0 J2EE APIs
(if you are not familiar with this big FUBAR-style transition, read
f.ex
https://blogs.oracle.com/javamagazine/transition-from-java-ee-to-jakarta-ee).
I am working with Sonatype admins to see if the problem might be in
Nexus repository's publishing, as well as Marc M who implemented
post-processing to create 2 jars, to see how to resolve the problem.
This may result in either fix for 2.12.2, or, possibly, release of
2.12.2.1 micro-patches for affected modules.
Also: for JSON-P module, specifically, I decided to go different route
so that there are TWO distinct artifacts:
* `jackson-datatype-jsr353`: old `javax.json` JSONP API type supporting module
* `jackson-datatype-jakarta-jsonp`: new `jakarata.json` JSONP APP API
type supporting module
which does not use classifier solution. For Jackson 3.0 we may want to
go with only supporting Jakarta variants, but that is
still to be Discussed and Decided.
-+ Tatu +-