Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 352411

Summary: Dependency Hierarchy doesn't resolve dependencies from workspace
Product: z_Archived Reporter: Konrad Windszus <konrad_w>
Component: m2eAssignee: Igor Fedorenko <igor>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: igor
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Konrad Windszus CLA 2011-07-19 04:25:13 EDT 
Build Identifier: 20110615-0604

If have a project B depending on project A, the dependency hierarchy tab of project B will only show transitive dependencies of A after A was installed to the local maven repo.
Expected would be a workspace resolution of project B (therefore displaying transitive dependencies immediately) without needing to run maven install first.

Reproducible: Always

Steps to Reproduce:
1. Create Maven Project A
2. Create Maven Project B
3. Insert Dependency to A into B
4. Maven install both
5. Have a look at the dependency hierarchy of B (no transitive dependencies -> correct)
6. Add a dependency to A, save the pom
7. Have a look at the dependency hierarchy of B (no transitive dependencies -> incorrect)
Comment 2 Denis Roy CLA 2021-04-19 13:25:32 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/