Community
Participate
Working Groups
If the STEM-workspace contains a space there are the following problems: Changes to to STEM-objects in the editor are not always propagated to the project explorer, for example: if you add a model to a scenario, the model does not appear in the scenario in the project explorer. This is because the URI of some objects contains the path with the space, which causes problems in comparing URIs.
Chris, are you seeing this when the workspace path has a space in it (and, by default, STEM has a space in the path)... like putting STEM at C:\program files\STEM
(In reply to comment #1) > Chris, are you seeing this when the workspace path has a space in it (and, by > default, STEM has a space in the path)... like putting STEM at C:\program > files\STEM Yes, exactly.
I'm able to reproduce this on Mac too. The problem is the EMF Resource class getURI() method is not able to return a platform URI (platform:/resource/<project>...) when the resource is stored in a path with a space it. Instead it returns the absolute path (file://...), that's what causing the problem. We won't fix this for the 1.2.1 release, it'll be documented instead. Might be an EMF bug.
let's resolve this one way or another for 1.2.3 I'm not sure it is a bug. If we want to ensure support across OS perhaps we should not allow spaces in the path?
This is not a STEM bug. Eclipse does not allow a Space character in workspace path. I updated the wiki to let users know of this.