Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368075 - The dependency could not be determined if using property in groupId or artifactId
Summary: The dependency could not be determined if using property in groupId or artifa...
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-07 04:36 EST by JasonMing CLA
Modified: 2021-04-19 13:25 EDT (History)
1 user (show)

See Also:


Attachments
Some screenshots of this issues (30.08 KB, application/octet-stream)
2012-01-07 04:36 EST, JasonMing CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description JasonMing CLA 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.
Comment 1 Igor Fedorenko CLA 2013-09-29 09:55:38 EDT
closing old/stale bugreports
Comment 2 Denis Roy CLA 2021-04-19 13:25:24 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/