Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340134 - StandaloneSetup does not resolve URIs correctly on Windows
Summary: StandaloneSetup does not resolve URIs correctly on Windows
Status: RESOLVED FIXED
Alias: None
Product: EMFT
Classification: Modeling
Component: MWE (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows All
: P3 blocker (vote)
Target Milestone: M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-16 06:00 EDT by Jan Koehnlein CLA
Modified: 2011-08-25 09:14 EDT (History)
1 user (show)

See Also:
jan: indigo+

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 Jan Koehnlein CLA 2011-03-16 06:00:33 EDT 
In the StandaloneSetup, we map classpath entries to platform:/resource URIs. 
In Windows this does not work, as File.getCanonicalPath() returns windows file separators resulting in invalid jar:/ URIs being mapped.

As a result, workflows to generate the Xtext infrastructure of languages using Xbase don't run on windows at all. This will render most M6 achievements of Xtext unavailable for Windows users.
Comment 1 Sebastian Zarnekow CLA 2011-07-14 16:34:31 EDT 
I take this one was fixed for Indigo final?
Comment 2 Sebastian Zarnekow CLA 2011-08-25 09:14:44 EDT 
Marked as fixed. Please reopen if the problem is still open.