How to deal with the message "omitted for conflict with .." in pom.xml?

Question

I have this situation:

I know that "Maven resolves version conflicts with the strategy for the coming victories." So here aop 3.0.7 wins based on this rule. But I also define the dependencyManagement section in my pom, and it looks like this:

<properties> <org.springframework.version>3.2.4.RELEASE</org.springframework.version> <org.springframework.security.version>3.1.4.RELEASE</org.springframework.security.version> </properties> <dependencyManagement> <dependencies> <dependency> <groupId>com.springframework</groupId> <artifactId>spring-aop</artifactId> <version>${org.springframework.version}</version> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-webmvc</artifactId> <version>${org.springframework.version}</version> </dependency> <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-web</artifactId> <version>${org.springframework.security.version}</version> </dependency> <dependency> <groupId>org.springframework.security</groupId> <artifactId>spring-security-config</artifactId> <version>${org.springframework.security.version}</version> </dependency> <dependency> <groupId>jstl</groupId> <artifactId>jstl</artifactId> <version>1.2</version> </dependency> <dependency> <groupId>org.codehaus.jackson</groupId> <artifactId>jackson-mapper-asl</artifactId> <version>1.7.1</version> </dependency> </dependencies> </project> 

And it all looks in the dependencies tab:

So, I expect spring -aop to use version 3.2.4.RELEASE instead of 3.0.7, like webmvc, as I define this in dependency management. Why is the older version 3.0 +0.7 still used?

Answer 1

Your dependency management statement has a typo (com.springframework instead of org.springframework).

This is the correct pom entry:

 <dependency> <groupId>org.springframework</groupId> <artifactId>spring-aop</artifactId> <version>3.2.4.RELEASE</version> </dependency> 

Unfortunately, since the dependency is not used, Maven (or Eclipse) will not mark it as a missing artifact.