Maven Dependency Resolution Is Not Working Properly -


as far read top level depths should chosen. can see below second level chosen. missing something?

enter image description here

you're right, should have worked per dependency mediation rules, doesn't, because of constraints on jersey-spring.pom (see here).

the constraint allows versions 2.5.2 thru 3 of spring-core used itself.

<spring25-release-version>[2.5.2,3)</spring25-release-version>

<dependency>   <groupid>org.springframework</groupid>   <artifactid>spring-core</artifactid>   <version>${spring25-release-version}</version>   <scope>compile</scope> </dependency> 

if know 4.1.7.release of spring-core plays 1.19 of jersey-spring, can try "managing" dependency , use did.

<dependencymanagement>   <dependencies>     <dependency>       <groupid>org.springframework</groupid>       <artifactid>spring-core</artifactid>       <version>4.1.7.release</version>     </dependency>   </dependencies> </dependencymanagement> 

dependency management trumps other means.


Comments

Popular posts from this blog

python - Healpy: From Data to Healpix map -

c - Bitwise operation with (signed) enum value -

xslt - Unnest parent nodes by child node -