Community
Participate
Working Groups
Given project "Inner" physically located inside project "Outer". If one browses to "Outer" within the import existing project wizard, "Inner" does not appear in the list of projects to import, only "Outer" does. To consistently support nested projects, this should work. The current behavior is annoying and there is no workaround other than manually importing each level of nested projects recursively.
Fixing this really depends on clarifying the semantics for physically nested projects. I propose the semantics suggested by bug 245412 comment 4 (masking out the folder of the physically nested project from its container, thus not producing overlap). With these semantics, *any* .project file in a folder hierarchy is a candidate for project import, regardless of whether it's nested below another .project file or not. This should simplify the wizard as well as user experience.
This might work already. PW
*** Bug 329991 has been marked as a duplicate of this bug. ***
This seems related to (or a duplicate of) bug 283368.
(In reply to comment #4) Agreed, the request in this bug is for importing physically nested projects, and there's a patch on bug 283368. Any core.resources change is somewhat orthogonal. *** This bug has been marked as a duplicate of bug 283368 ***
As I read this, the request is just about the import wizard allowing to show nested project (.project) files when importing. It's a pure-UI operation and is not related to how resource are stored or displayed in Eclipse. So it's not at all a dup of bug 245412. In the project import wizard, I can see a "Search for nested projects" checkbox which allows to do what's requested in comment 0. So I'll removing dependency/duplicate links to bug 245412.
