Bug 368075

Description JasonMing 2012-01-07 04:36:13 EST

Created attachment 209164 [details]
Some screenshots of this issues

I declared the dependencyManagement in parent project:
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>${project.groupId}</groupId>
        <artifactId>common</artifactId>
        <version>${project.version}</version>
        <scope>provided</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

and reference in the module:
  <dependency>
    <groupId>${project.groupId}</groupId>
    <artifactId>common</artifactId>
  </dependency>

1. in module's "pom.xml" tab while mouse hover on the above dependency, prompts：
  "The managed version could not be determined. The managed definition location could not be determined, probably defined by "import" scoped dependencies."

2. in moudle's "Dependencies" tab could not determine the dependency (If the dependency is managed, a lock will appear in left-bottom corner of icon and prompt that dependency is managed， however the dependency is detemined in this tab as a non-managed dependency)

3. in module's "Dependency Hierarchy" and "Effective POM" tab can normally determine the dependency.


In above case, while mouse hover on the reference of property, it can still determine the value of the property.
If I use a constant value like "com.abc" instead of the property, then all of above problem will be resolved.
It seems that that m2e plugin cannot determine the property in groupId and artifactId well.