Plivo API incompatible with spring-boot version 4+

[martinisraelsen]

In the process of upgrading to Spring Boot V 4 and getting this error message when trying to launch Plivo:

Caused by: java.lang.NoSuchFieldError: Class com.fasterxml.jackson.databind.PropertyNamingStrategy does not have member field 'com.fasterxml.jackson.databind.PropertyNamingStrategy SNAKE_CASE' at com.plivo.api.PlivoClient.<init>(PlivoClient.java:99) ~[plivo-java-5.46.3.jar:5.46.3] at com.plivo.api.PlivoClient.<init>(PlivoClient.java:242) ~[plivo-java-5.46.3.jar:5.46.3] at com.plivo.api.Plivo.init(Plivo.java:15) ~[plivo-java-5.46.3.jar:5.46.3]

[jswoyer-bushel]

Any movement on this? Any easy workarounds?

[martinisraelsen]

Joshua Swoyer (@jswoyer-bushel) We ended up adding Jackson-core (3.x) as well as Jackson 2.x explicitly. Spring will use the 3.x and Plivo is using the 2.x. The class names are different in 3.x so there is no conflict. Would still prefer Plivo to get upgraded.

<!-- Explicit Jackson 3.x dependency (needed since Plivo is dependent on Jackson 2.x) -->
  <dependency> 
    <groupId>tools.jackson.core</groupId>
    <artifactId>jackson-core</artifactId>
  </dependency>

<!-- Plivo requires Jackson 2.x -->
  <dependency>
    <groupId>com.fasterxml.jackson.core</groupId>
    <artifactId>jackson-core</artifactId>
    <version>2.21.2</version>
  </dependency>

  <dependency>
    <groupId>com.fasterxml.jackson.core</groupId>
    <artifactId>jackson-annotations</artifactId>
    <version>2.21</version>
  </dependency>
	    
  <dependency>
    <groupId>com.fasterxml.jackson.core</groupId>
    <artifactId>jackson-databind</artifactId>
    <version>2.19.4</version>
  </dependency>
<!-- // plivo-jackson support -->

[TechnicalRhino]

Confirming this reproduces on Spring Boot 3.5.13 too — not just Spring Boot 4. Spring Boot 3.5.13 manages jackson-bom 2.21.2, which is enough to trigger the crash.

Root cause (for anyone else landing here): Jackson 2.20 removed the deprecated static constant PropertyNamingStrategy.SNAKE_CASE. It was superseded back in Jackson 2.12 by PropertyNamingStrategies.SNAKE_CASE (note the plural class name). Jackson 2.19.x still carries the old field as deprecated; 2.20+ does not.

PlivoClient.java:99 still references the removed constant:

// current (broken on Jackson >= 2.20)
.setPropertyNamingStrategy(PropertyNamingStrategy.SNAKE_CASE)

// fix
.setPropertyNamingStrategy(PropertyNamingStrategies.SNAKE_CASE)

That one-line change (plus the matching import com.fasterxml.jackson.databind.PropertyNamingStrategies;) restores compatibility with Jackson 2.12 through 2.21.x without breaking older consumers, since PropertyNamingStrategies has existed since 2.12. Happy to open a PR if that helps.

Simpler workaround than mixing Jackson 2.x and 3.x — pin jackson-bom to 2.19.x in your own pom. Spring Boot's dependency management resolves Jackson via the jackson-bom.version property, so a single override is enough:

<properties>
    <jackson-bom.version>2.19.2</jackson-bom.version>
</properties>

Verify with mvn dependency:tree | grep jackson-databind — should show 2.19.2.

This is clearly affecting more than a handful of users at this point — would really appreciate a patch release with the one-liner above.

[jswoyer-bushel]

Agni (@TechnicalRhino) I actually already opened a PR unfortunately. Still no news or feedback. Not sure if I did something wrong with the PR process, but it'd be nice to hear SOMETHING back, even just acknowledgement of the issue.

[narayana-plivo]

Joshua Swoyer (@jswoyer-bushel) Martin Israelsen (@martinisraelsen) Agni (@TechnicalRhino) We have deployed the change. Please use the latest version, v5.48.0

[jswoyer-bushel]

Narayana Shanbhog Plivo (@narayana-plivo) Is this being published on maven? I'm not seeing anything newer than 5.46.3 (october 2025): https://mvnrepository.com/artifact/com.plivo/plivo-java/versions