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

Bug 353542

Summary:	StandaloneSetup not robust in case of ambiguous .project file
Product:	[Modeling] EMFT	Reporter:	Boris holzer <boris.holzer>
Component:	MWE	Assignee:	Project Inbox <emft-mwe-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Boris holzer

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