javax.json dependency or lack of

[visionset]

JSR353Module.java has a direct javax.json import, but the pom does not have that dependency, only in test scope, and really why not come upto date and use jakarta.json ?
Our builds now fail having swapped from javax.json to jakarta.json in our own codebase, and hence the java.json jar is now not present.

Caused by: java.lang.NoClassDefFoundError: javax/json/spi/JsonProvider
at com.fasterxml.jackson.datatype.jsr353.JSR353Module.(JSR353Module.java:24)

[cowtowncoder]

javax.json is incompatible with jakarta.json -- for latter there is separate module:

https://github.com/FasterXML/jackson-datatypes-misc/tree/2.x/jakarta-jsonp

JSONPModule

2 separate modules are needed because Jakarta change is a god-forsaken clusterf**k, REALLY really badly executed change.
This way we can support old and new cases (more so wrt JAXB, JAX-RS, JSONP is not as widely used). Otherwise it is impossible to support use via both pre-Jakarta and Jakarta APIs/Impls.

Question of dependency for "old" JSR353Module is a separate issue: I forget whether this is intentional (we do not pull in implementation, just API) or accidental.

But for your use it should be irrelevant as you will want to switch to the new module.

[visionset]

thanks, that change has worked perfectly