new ObjectMapper().readTree() throws exceptions since v2.15.1 (fixed in 2.15.2)

[sblantipodi]

Describe the bug
My software works since years, I updated to databind v2.15.1 and it started throwing exceptions.

Version information
2.15.1

To Reproduce

ObjectMapper mapper = new ObjectMapper();
JsonNode mqttmsg = mapper.readTree(message.getPayload());

where message is MqttMessage from org.eclipse.paho.client.mqttv3 and getPayload() returns byte[].

I have the same problem even with a simple thing like this:
mapper.readTree("{'pippo':'pluto'}");

this is the exception thrown:
java.lang.ClassNotFoundException: com.fasterxml.jackson.core.exc.StreamConstraintsException

this is my POM.xml...

<jackson.version>2.15.1</jackson.version>
<jackson.dataformat.version>2.14.2</jackson.dataformat.version>
<jackson.module.version>2.14.2</jackson.module.version>
<jackson.datatype.version>2.14.2</jackson.datatype.version>

I can't find the update for the other modules in mavencentral

Expected behavior
have it working as always.

[JooHyukKim]

@sblantipodi There must be a mismatch between versions. Could you just try upgrading all Jackson moudles to 2.15 and try again?

I may have to double check tho, but com.fasterxml.jackson.core.exc.StreamConstraintsException might have been introduced in 2.15

[sblantipodi]

ok I manually updated everything to 2.15.1

<jackson.version>2.15.1</jackson.version>
<jackson.dataformat.version>2.15.1</jackson.dataformat.version>
<jackson.module.version>2.15.1</jackson.module.version>
<jackson.datatype.version>2.15.1</jackson.datatype.version>

but now it doesn't compile:
\src\main\java\module-info.java:14:35 java: module not found: com.fasterxml.jackson.core

[sblantipodi]

@JooHyukKim 2.15.0 works well...
2.15.1 destroyed everything :D

[pjfanning]

this is FasterXML/jackson-core#1027

You'll need to wait until jackson 2.15.2, I'm afraid.

[JooHyukKim]

You'll need to wait until jackson 2.15.2, I'm afraid.

Right, as @pjfanning mentions.

I wonder if there is anything we can do, to advise users running into the same issue. 🤔🤔

[sblantipodi]

ok thanks for the answer :)

[cowtowncoder]

I am planning to release 2.15.2 this week; hopefully today or tomorrow. Fwtw.

Note that the original problem was a simple incompatibility between deployed versions: one MUST NOT try to use older minor version of jackson-core than jackson-databind -- that will not work, is not meant to work.

But there is indeed #1027 which can prevent use on Module-enabled set ups (which means tons of users) :-/

[sblantipodi]

@cowtowncoder thanks for the answer.
not all the jackson modules has been pushed on Maven Central at the same time, or IntelliJ doesn't seen the update at the same time.

IntelliJ suggested me an update and I accepted it just to try, for this reason I ended up with this versions:

<jackson.version>2.15.1</jackson.version>
<jackson.dataformat.version>2.14.2</jackson.dataformat.version>
<jackson.module.version>2.14.2</jackson.module.version>
<jackson.datatype.version>2.14.2</jackson.datatype.version>

Glad to see that 2.15.2 is imminent that will fix the 2.15.1 compile error.

[cowtowncoder]

@sblantipodi It may indeed take 2-3 hours for a complete set to be available, it should never lead to use of inconsistent set, please don't do that. IntelliJ has no idea of constraints (unless you use jackson-bom which is highly recommended). It is too bad Idea suggests use of mismatching versions.

But specifically you should avoid mixing minor versions (2.15 vs 2.14).

[sblantipodi]

closing since the issue is now solved.