Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352411 - Dependency Hierarchy doesn't resolve dependencies from workspace
Summary: Dependency Hierarchy doesn't resolve dependencies from workspace
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Fedorenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-19 04:25 EDT by Konrad Windszus CLA
Modified: 2021-04-19 13:25 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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/