Bug 344703

Description Cuong Luu 2011-05-04 09:45:45 EDT

Build Identifier: 20090920-1017

Consider the following.
1) parent POM that contains dependencies that all have version ranges, e.g.
<dependency>
  <groupId>third.party</groupId>
  <artifactId>third.party.lib</artifactId>
  <version>[4, 5)</version>
  <scope>provided</scope>
</dependency>
2) project1 inherits parent POM as a parent, e.g.
<parent>
  <groupId>test.group</groupId>
  <artifactId>parent</artifactId>
  <version>1.0.0</version>
</parent>
3) project2 also inherits parent POM and defines a dependency on project1.

All this is fine when I use maven command line to deploy to my repository.

Now, I use Eclipse (with m2eclipse) to check out project2 and Enable Dependency Management.
Here are the problems.
a) If project2 defines project1 version as 1.0.0 - SUCCESS
b) If project2 defines project1 version as [1,2) - FAILS
c) If I remove the third.party.lib dependency from the parent POM - SUCCESS on both of the a) and b).

The error it has is that it can't find the third.party.lib artifact, even though the POM for the artifact has been download (but NOT the jar itself).

Reproducible: Always