| Summary: | hierarchical projects | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Christian Pekeler <christian> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | 3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | All | ||
| Whiteboard: | |||
It would be useful for Eclipse to support hierarchical projects, i.e. projects of projects. Projects are often organized like this: company/ projectA/ applications/ appA1/ appA2/ frameworks/ frameworkA1/ frameworkA2/ frameworkA3/ projectB/ applications/ appB1/ appB2/ appB3/ frameworks/ frameworkB/ with ant build scripts on each level, so that if I'm in appB2, ant will build that app, and if I'm in company, ant will build everything beneath it. Eclipse seems to only be able to deal with a flat project structure, so the above example would look like: appA1/ appA2/ frameworkA1/ frameworkA2/ frameworkA3/ appB1/ appB2/ appB3/ frameworkB/ This flat representation is confusing, because it looks different than the original hierarchy. It makes ant build scripts unusable if they have relative paths to neighboring projects. And trying to map Eclipse's flat view of the world to a hierarchical structure in the filesystem is a pain to set up (especially when everything is version controlled via Eclipse).