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

Bug 341253

Summary: better support cross-project resource references
Product: z_Archived Reporter: Igor Fedorenko <igor>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
sample project to demonstrate the problem none

Description Igor Fedorenko CLA 2011-03-29 12:06:07 EDT 
Created attachment 192110 [details]
sample project to demonstrate the problem

Originally reported as http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00410.html

Quick analysis. module-a project references resources from module-b, this is generally considered a bad practice and discouraged. Even though I do not believe m2e should "help" users do this, I think m2e can provide some limited support.
Comment 1 Igor Fedorenko CLA 2011-03-29 13:33:11 EDT 
Done. 

Fix: http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=3f2dd8a600d058419b42ff25d7afbe09854f7efd
Test: https://github.com/sonatype/m2e-core-tests/commit/8a10e46b8c9365dc03ba040561a8c6c71c40f984


Do note that this implementation only supports cross-project resource filtering during full/clean workspace builds. Properly supporting this during incremental workspace builds is much harder problem.
Comment 2 Denis Roy CLA 2021-04-19 13:23:04 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/