jackson-databind 2.9.1 includes old version of jackson-core and jackson-annotations

[INFO] +- com.fasterxml.jackson.core:jackson-databind:jar:2.9.1:compile
[INFO] |  +- com.fasterxml.jackson.core:jackson-annotations:jar:2.8.0:compile
[INFO] |  \- com.fasterxml.jackson.core:jackson-core:jar:2.8.10:compile

Problem caused will be attached later. Workaround is to explicitly declare latest dependencies to override them.

        <dependency>
            <groupId>com.fasterxml.jackson.core</groupId>
            <artifactId>jackson-core</artifactId>
            <version>2.9.1</version>
        </dependency>
        <dependency>
            <groupId>com.fasterxml.jackson.core</groupId>
            <artifactId>jackson-annotations</artifactId>
            <version>2.9.1</version>
        </dependency>

[cowtowncoder]

@codingsince1985 Ah. Hmmh. That makes more sense. Interesting… there’s some unfortunate interaction there between definition of jackson.version by jackson-parent and spring boot. I don’t know what would be the best way to resolve that.

One thing that might help would be to use jackson-bom project:

http://mvnrepository.com/artifact/com.fasterxml.jackson/jackson-bom

either by importing it (it’s a pom artifact designed to provide consistent set of versions), or using as parent pom. Either way would give you dependencyManagement section with versions defined for all official jackson components. It also does set jackson.version consistently.

[hzsbrave]

<dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-databind</artifactId> <version>2.9.4</version> </dependency> <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-core</artifactId> <version>2.9.4</version> </dependency> <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-annotations</artifactId> <version>2.9.4</version> </dependency> add both dependency