Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353082 - Workspace resolution does not kick in when a project is opened
Summary: Workspace resolution does not kick in when a project is opened
Status: CLOSED DUPLICATE of bug 350956
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: All Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-26 04:19 EDT by Steve CLA
Modified: 2021-04-19 13:26 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve CLA 2011-07-26 04:19:01 EDT 
I have a workspace with a webapp and a library, the webapp references the library in its pom.xml. When I open the library project I expect the workspace resolution to kick in and the dependency to be converted to use the project, rather than a jar file, but this no longer happens.

After changing and saving the pom files of one or the other, it normally does kick in and the proper dependency made.

I am using Eclipse 3.7 with:
m2e - Maven Integration for Eclipse	1.0.0.20110607-2117	org.eclipse.m2e.feature.feature.group	Eclipse.org - m2e

This used to work fine with 3.6 and the Sonatype m2eclipse.

Thanks,

Steve
Comment 1 Igor Fedorenko CLA 2011-07-26 04:29:45 EDT 
latest snapshot towards indigo sr1 can be installed from https://repository.sonatype.org/content/repositories/forge-sites/m2e/1.0.100/N/LATEST/

*** This bug has been marked as a duplicate of bug 350956 ***
Comment 2 Denis Roy CLA 2021-04-19 13:26:23 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/