Bugzilla – Full Text Bug Listing
| Summary: | unable to open .dot file | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Tools] GEF | Reporter: | David Samuelsson <david.samuelsson.se> | ||||||
| Component: | GEF-Legacy Zest | Assignee: | gef-inbox <gef-inbox> | ||||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | steeg | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
David Samuelsson
Created attachment 237677 [details]
eclipse config
seems my description got lost? I needed to look at some genereated .dot files so i installed zest 2.0.0 from the marketplace. but got erors when trying to load the view Guice provision errors: 1) Error injecting constructor, org.eclipse.emf.common.util.WrappedException: org.eclipse.xtext.resource.ClasspathUriResolutionException: java.lang.IllegalStateException: Couldn't find resource on classpath. URI was 'classpath:/org/eclipse/gef4/zest/internal/dot/parser/Dot.xmi' at org.eclipse.gef4.zest.internal.dot.parser.services.DotGrammarAccess.<init>(Unknown Source) at org.eclipse.gef4.zest.internal.dot.parser.services.DotGrammarAccess.class(Unknown Source) while locating org.eclipse.gef4.zest.internal.dot.parser.services.DotGrammarAccess while locating org.eclipse.xtext.IGrammarAccess see error.txt for full stacktrace Created attachment 237681 [details]
error when opening any .dot file
I've seen similar issues before with some versions of Xtext (which pulls in Guice). Perhaps you already had some incompatible version of Xtext or Guice installed? You could try uninstalling both Zest and Xtext, or start from a clean package. Or did you install into a clean package? yepp after fresh install of eclipse via chocolatey http://chocolatey.org/packages/eclipse-standard-kepler (try this btw, really neat packaging method for windows) then only installed zest, then it worked. Seems there must have been something conflicting in my setup, even though everything is installed via p2. works for me |