I created a new Test project having only apache-jena-libs as dependency. Then 1.5 is pulled correctly within the dependency tree. So there has to be a dependency that is closer to my application that pulls 1.3 but how to get to this info?
Johan, Op wo 20 jan. 2021 om 23:43 schreef Johan Kumps <johan.ku...@telenet.be>: > I really don't get it. > > Using the mvn dependency:tree -Dverbose -Dincludes=commons-codec I trace > the 1.3 version back to jena-base: > > [INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ > spring-jena-starter --- > [INFO] Verbose not supported since maven-dependency-plugin 3.0 > [INFO] my.application:spring-jena-starter:jar:0.0.1-SNAPSHOT > [INFO] \- org.apache.jena:apache-jena-libs:pom:3.17.0:compile > [INFO] \- org.apache.jena:jena-shacl:jar:3.17.0:compile > [INFO] \- org.apache.jena:jena-arq:jar:3.17.0:compile > [INFO] \- org.apache.jena:jena-core:jar:3.17.0:compile > [INFO] \- org.apache.jena:jena-base:jar:3.17.0:compile > [INFO] \- commons-codec:commons-codec:jar:1.13:compile > > Even when I add 1.5 to my pom I get the same error. When I show the > effective pom in IntelliJ it mentions 1.3 even when I explicitly add 1.5 in > my project pom. > > Johan, > > Op wo 20 jan. 2021 om 23:34 schreef Andy Seaborne <a...@apache.org>: > >> There is an example of choosing an older version because it is nearer >> despite being both older and later in the tree >> >> >> https://maven.apache.org/plugins/maven-dependency-plugin/examples/resolving-conflicts-using-the-dependency-tree.html >> >> so >> >> mvn dependency:tree -Dverbose -Dincludes=commons-codec >> >> may help >> >> Andy >> >
