Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353542 - StandaloneSetup not robust in case of ambiguous .project file
Summary: StandaloneSetup not robust in case of ambiguous .project file
Status: NEW
Alias: None
Product: EMFT
Classification: Modeling
Component: MWE (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 04:05 EDT by Boris holzer CLA
Modified: 2011-08-02 04:05 EDT (History)
0 users

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 Boris holzer CLA 2011-08-02 04:05:30 EDT 
Build Identifier: 

StandaloneSetup.setPlatformUri scans all folders below the "PlatformURI" in order to find .project files which in turn are put into the EcorePlugin.getPlatformResourceMap(). In case of several .project files describing the same project (i.e. with identical name), the .project scanned last survives in the PlatformResourceMap.

My expectation was, that only projects residing at the top level in the folder denoted by the PlatformURI were scanned. 

Reproducible: Always

Steps to Reproduce:
1. In Eclipse: Create a new Xtext Project 
2. Within OS' file explorer:
   2.1. Within your workspace, create a new folder "projectsIWantToIgnore"
   2.2. Copy the folder containing the Xtext project into the new folder.
3. In Eclipse: Launch Xtext Project's mwe2 workflow 
4. Find generated EMF classes in the copy created in step 2.2, but not in Eclipse project