Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364753 - GrammarAccessFragment should not build a URI from path
Summary: GrammarAccessFragment should not build a URI from path
Status: NEW
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.1.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-24 15:23 EST by Benjamin Schwertfeger CLA
Modified: 2011-11-25 03:32 EST (History)
1 user (show)

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 Benjamin Schwertfeger CLA 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.