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

Bug 126283

Summary: support for nested projects
Product: [Eclipse Project] Platform Reporter: Iyad Elian <IyadElian>
Component: ResourcesAssignee: Platform-Resources-Inbox <platform-resources-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: dev
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Iyad Elian CLA 2006-02-02 17:19:20 EST 
Eclipse flat project structure is so frustrating, yes you can set a different output folder and you can link in another folder but a nested subproject is much more than that. the abvious use case is the test folder which not only has a different src folder and output but also has its own dependency (junit)
so the project is
<project>/.classpath (no junit.jar and will not compile test classes)
<project>/java/src
<project>/java/classes

and the nested subproject
<project>/test/.classpath (includes junit)
<project>/test/java/src
<project>/test/java/classes

another use case is the plugin update and features which have to live outside the project they belong to.
what will it take to support nested projects?
Comment 1 John Arthorne CLA 2006-02-02 17:35:32 EST 

*** This bug has been marked as a duplicate of 35973 ***
Comment 2 Iyad Elian CLA 2006-02-02 18:50:37 EST 
I got a headache just from reading the other bug. the description here is clear , consice and has clear straight forward use cases. I would like to see an action as the other one was left hanging.
let me know how I can help.
Comment 3 John Arthorne CLA 2006-02-03 09:33:18 EST 
Sorry, but this really is a duplicate of bug 35973.  The discussion in that bug is long, but it is more complicated than it appears.  You may also be interested in bug 44967, which was fixed in 3.2 stream (allowing projects to overlap on disk).

*** This bug has been marked as a duplicate of 35973 ***