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

Bug 364753

Summary:	GrammarAccessFragment should not build a URI from path
Product:	[Modeling] TMF	Reporter:	Benjamin Schwertfeger <benjamin.schwertfeger>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	P3	CC:	christian.dietrich.opensource
Version:	2.1.0
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Benjamin Schwertfeger

2011-11-24 15:23:09 EST

In the generated Workflow the value for runtimeProject and platformUri are relative paths. In the GrammarAccessFragment the value is interpreted as an URI and for the StandaloneSetup and other Fragments it's a path.

The GrammarAccessFragment tries URI.createURI with something build of pathRtProject, which sounds like a path. Under Windows the path contains a "C:" which is interpreted as a protocol.

The ParseTreeConstructorFragment tries new File with the same construct as GrammarAccessFragment uses. In this case and also for the StandaloneSetup and the generator it needs to be a path.

You can see the Problem on windows, if you set a not relative path. This is neccessary in maven if you build modules for example.