Community
Participate
Working Groups
I installed Xtext through the Eclipse Marketplace, and started to follow the user guide here: http://www.eclipse.org/Xtext/documentation/latest/xtext.html After following the directions in the section "Create an Xtext Project", my project was created, but it is littered with errors in the *.xtext and *.mwe2 files. All of these errors start with "Couldn't resolve reference to...". Here are a few examples: Couldn't resolve reference to Grammar 'org.eclipse.xtext.common.Terminals'. Couldn't resolve reference to AbstractRule 'ID'. Couldn't resolve reference to JvmFeature 'bean'. Couldn't resolve reference to JvmType 'builder.BuilderIntegrationFragment'. Eclipse: Eclipse IDE for Java Developers Version: Helios Release Build id: 20100617-1415 File: eclipse-java-helios-macosx-cocoa-x86_64.tar.gz Java: java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-9M3165) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode)
Please close the editor and try a clean build. Should be a race-condition with the JDT initialization.
(In reply to comment #1) > Please close the editor and try a clean build. Should be a race-condition with > the JDT initialization. I restarted Eclipse many times over trying to diagnose the problem, but the problem still persists. Also, I'm not sure what you mean by a "clean build"... you mean a clean build of Eclipse? This was a brand new installation of Eclipse. The very first thing I did was install Xtext and try to create a new Xtext project.
(In reply to comment #2) > Also, I'm not sure what you mean by a "clean build"... Please go to the project menu and choose Clean ... The error markers should disappear afterwards.
(In reply to comment #3) > (In reply to comment #2) > > Also, I'm not sure what you mean by a "clean build"... > > Please go to the project menu and choose Clean ... > The error markers should disappear afterwards. Yes, I have tried that too, however, the problem remains.
*** This bug has been marked as a duplicate of bug 318273 ***
see also bug 317301