Skip to content
9 changes: 7 additions & 2 deletions pom.xml
Original file line number Diff line number Diff line change
Expand Up @@ -131,15 +131,20 @@
<artifactId>json</artifactId>
<version>20231013</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-annotations</artifactId>
<version>2.19.0</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.17.0-rc1</version>
<version>2.19.0</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-core</artifactId>
<version>2.17.0-rc1</version>
<version>2.19.0</version>
</dependency>
Comment on lines 145 to 148
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ› οΈ Refactor suggestion

Mixed Jackson versions: Consider alignment or BOM management

While you’ve upgraded jackson-core to 2.19.0, other modules (annotations, databind, datatype-joda) must all share the same version to avoid classpath conflicts. If you intend to pin versions manually, ensure every Jackson artifact is at 2.19.0. A cleaner approach is to remove explicit Jackson versions here and let Spring Boot’s dependency management (parent POM) enforce a consistent, tested Jackson version set.

πŸ€– Prompt for AI Agents
In pom.xml around lines 140 to 143, the jackson-core version is set to 2.19.0
while other Jackson modules have different versions, causing potential
conflicts. To fix this, either update all Jackson dependencies (annotations,
databind, datatype-joda) to version 2.19.0 for consistency or remove the
explicit version tags from all Jackson dependencies and rely on Spring Boot's
parent POM to manage and align the Jackson versions automatically.


<dependency>
Expand Down
Loading