|Re: org.eclipse.jdt.internal.compiler.problem.AbortCompilation: Pb(324) The type org.eclipse.xtext.g [message #1245216 is a reply to message #1237017]
||Thu, 13 February 2014 13:20
| Aaron Digulla
Registered: July 2009
Today, I had some time to debug Eclipse and Xtext. It turns out that the resource which Xtext tries to "build" is DslGeneratorMWE.mwe2.|
In my project, DslGeneratorMWE.mwe2 is in the folder resources/ which is part of the sources to include in the build (along with the .xtext grammar).
When location DSL resources on the classpath, XtextBuilder sees this file and tries to start the MWE2 workflow parser.
I see two solutions:
1. Adding the MWE2 plugin to the classpath "somewhere".
2. Removing the *.mwe2 file from the plugin
I tried both:
I moved the *.mwe2 file from the resource folder to the root of the DSL plugin. When I do that, then MWE2 can't execute it anymore (the error says that MWE2 can't find the file).
I added org.eclipse.emf.mwe.core to the DSL runtime and UI plugins but that didn't help. My guess it that I'd have to add it to the classpath of the project which contains the DSL file (i.e. not at the side where the DSL editor is developed but on the side where the DSL editor is used).
Is there a way to tell Tycho or Eclipse not to include the mwe2 file in the binary plugin?
Note: If you want to debug this, start an instance of Eclipse from the Eclipse in which you develop your DSL and set a breakpoint on this line:
org.eclipse.jdt.internal.core.util.Util.log(e, "Could not retrieve superclass"); //$NON-NLS-1$
inside of the method ITypeBinding getSuperclass() in the file org.eclipse.jdt.core.dom.TypeBinding (should be around line 814).
[Updated on: Thu, 13 February 2014 13:24]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.81113 seconds