That is because you didn't enforce maven to fail the build. Take a look at the dependencies plugin [1]
[1] http://maven.apache.org/plugins/maven-dependency-plugin/analyze-dep-mgt-mojo.html#failBuild Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Tue, Oct 20, 2009 at 11:39 AM, Borut Bolčina <borut.bolc...@gmail.com>wrote: > Hi, > > if in parent pom (company POM for example): > > <dependencyManagement> > <dependencies> > <dependency> > <groupId>com.acme</groupId> > <artifactId>coyote-tornado-kit</artifactId> > <version>[1.0.0]</version> > </dependency> > </dependencyManagement> > > and in some project: > > <dependencies> > <dependency> > <groupId>com.acme</groupId> > <artifactId>coyote-tornado-kit</artifactId> > <version>[2.0.0]</version> > </dependency> > </dependencies> > > then I would expect build to fail becouse hard versions are used. Why is > that not so? > > -Borut >
