deprecated usage of com.fasterxml.jackson.databind.PropertyNamingStrategies

[qwertiko]

Problem:

got an exception in Jenkins which is using gitlab4j-api in it's gitlab-source-plugin
java.lang.NoSuchFieldError: Class com.fasterxml.jackson.databind.PropertyNamingStrategy does not have member field 'com.fasterxml.jackson.databind.PropertyNamingStrategy SNAKE_CASE'

Analysis

I think the root cause lies in this project since it has com.fasterxml.jackson.core:jackson-databind as dependency. gitlab4j-api uses PropertyNamingStrategy.SNAKE_CASE in

gitlab4j-api/gitlab4j-api/src/main/java/org/gitlab4j/api/utils/JacksonJson.java

Line 63 in 7bd1d19

objectMapper.setPropertyNamingStrategy(PropertyNamingStrategies.SNAKE_CASE);

But as seen in https://github.com/FasterXML/jackson-databind/blob/43c6527773493e82e066cbe3d1e05f0344f437f0/src/main/java/com/fasterxml/jackson/databind/PropertyNamingStrategy.java#L54 this attribute is deprecated and removed. After some digging I found out that this project uses version 2.18.0

gitlab4j-api/gitlab4j-models/build.gradle

Line 3 in 7bd1d19

api 'com.fasterxml.jackson.core:jackson-databind:2.18.0'

Suggested Resolution

• downgrade version of jackson-databind to 2.10 since it is the current stable 2.x version
• remove usage of PropertyNaimingStrategy.SNAKE_CASE

Thanks!

[jmini]

I did not found any occurrences of PropertyNaimingStrategy.SNAKE_CASE in our codebase.

I don't follow why com.fasterxml.jackson.core:jackson-databind:2.10.0 would be better than com.fasterxml.jackson.core:jackson-databind:2.18.0.

Can you please elaborate on your "Suggested Resolution"?

[maxime-michel]

My team's CI is completely stopped with the same error after I ran a plugin update this morning. Would be great if a workaround could be found ASAP!

I don't know so much about 2.10.0 either, one thing I did see in my investigation is that this happened at the same time as the shift from 2.19.2 to 2.20.2 here: https://github.com/jenkinsci/jackson2-api-plugin/releases/tag/2.20.0-411.v6ef8fdee4fe9

FWIW those are the plugins I updated:

• aws-java-sdk2-core
• aws-java-sdk2-ec2
• jackson2-api
• pipeline-graph-analysis
• workflow-job
• workflow-durable-task-step

[fgrilli]

@jmini Hi, my team's CI has both GitLab API Plugin v5.6.0 and GitLab Plugin v1.9.9 installed.
The latter is using jackson-databind v2.20 where the property in question was removed after being deprecated since v2.12.

I would suggest you use PropertyNamingStrategies.SNAKE_CASE instead as they did in the GitLab plugin.

Cheers!

[maxime-michel]

FWIW we unblocked our CI by doing the above and then deploying a custom build of the Jenkins gitlab-api plugin building upon the SNAPSHOT. (Sorry if these Jenkins-centric discussions have nothing to do here, BTW.)

[fgrilli]

I did not found any occurrences of PropertyNaimingStrategy.SNAKE_CASE in our codebase.

Indeed main is using PropertyNamingStrategies.SNAKE_CASE but In our case we are on v5.6.0 which is still using the now removed API.
It would be great if you could cut a 5.6.1 release fixing this. 🙏

[apuig]

Hey everyone! 👋 This is my first time commenting here, so thanks for having me.

I’m facing a similar situation. It would be awesome for the Jenkins ecosystem if we could get a 5.6.x release that includes the fix for the Jackson deprecation. That would really help unblock plugin alignments in up-to-date environments.

There are efforts underway to migrate to 6.0.x, but there are some Jakarta updates involved (Jersey/JAXB), so having a quick 5.6.x release would be a huge help in the meantime.

I didn’t see a 5.6.x branch and I’m not sure what the usual contribution process is here. If you could point me in the right direction, I’d be happy to help out however I can!

Thanks!
cc @fgrilli @bguerin
#1281

[jmini]

I didn’t see a 5.6.x branch and I’m not sure what the usual contribution process is here. If you could point me in the right direction, I’d be happy to help out however I can!

Yes because I did not plan to do any maintenance on that old version...

---

It would have been easier if the Jenkins plugins maintainer would have told me when I announced to stop support of the 5.x.x stream here:
#926 (comment)

Maintaining 2 streams in parallel is way less work than coming a year later and seeking an update on this old version.

---

I could offer a release on top of 5.8.0, which is already very close to 5.6.0. I would still have to pack-port the move to jreleaser (#923) but this is probably possible.

[apuig]

Thanks for the quick reply, and totally understood: the inconvenience here is on our side, we missed the 5.x EOL signal, and I appreciate you considering a path forward anyway.

Good news: I tested 5.8.0 with the Jenkins gitlab-branch-source-plugin and it only needs a minor tweak. No issues with the newer dependencies, so a 5.8.x release would unblock many of us without waiting for the Jakarta/Jersey/JAXB changes required by 6.x.

If there’s any way I can help with this release request, I’m happy to support.

I’ll continue tracking the 6.x migration in parallel; this would just provide a safe intermediate step for current plugin users. Thanks again for considering it.