| J2SE-1.7 Problem [message #874982] |
Mon, 21 May 2012 22:31  |
 Ștefan Săftescu
Messages: 4
Registered: May 2012 |
Junior Member |
|
|
I've just found out about Xtext and I wanted to try it out. However, when I create an example project, I get the following build error (which doesn't seem very informative):
Errors running builder 'Xtext Project Builder' on project 'org.eclipse.xtext.example.fowlerdsl'.
org.eclipse.xtext.naming.QualifiedName.create(Ljava/lang/String;)Lorg/eclipse/xtext/naming/QualifiedName;
Furthermore, I have the following warnings in my project(s):
Build path specifies execution environment J2SE-1.5. There are no JREs installed in the workspace that are strictly compatible with this environment. org.eclipse.xtext.example.fowlerdsl
Build path specifies execution environment J2SE-1.5. There are no JREs installed in the workspace that are strictly compatible with this environment. org.eclipse.xtext.example.fowlerdsl.ui
Discouraged access: The type IPartialContentAssistParser is not accessible due to restriction on required library /home/stefan/.eclipse/org.eclipse.platform_3.7.0_1543616141/plugins/org.eclipse.xtext.ui.codetemplates.ui_2.3.0.v201205081025.jar PartialStatemachineContentAssistParser.java /org.eclipse.xtext.example.fowlerdsl.ui/src-gen/org/eclipse/xtext/example/fowlerdsl/ui/contentassist/antlr line 10
Discouraged access: The type IPartialContentAssistParser is not accessible due to restriction on required library /home/stefan/.eclipse/org.eclipse.platform_3.7.0_1543616141/plugins/org.eclipse.xtext.ui.codetemplates.ui_2.3.0.v201205081025.jar PartialStatemachineContentAssistParser.java /org.eclipse.xtext.example.fowlerdsl.ui/src-gen/org/eclipse/xtext/example/fowlerdsl/ui/contentassist/antlr line 18
I only have OpenJDK7 installed and that seems to be the problem. Could you confirm that is the case and, if so, is there any way I could fix this or should I just install OpenJDK6 or 5?
Edit: Here's a more informative version of the first error, which showed up today:
1 [main] ERROR mf.mwe2.launch.runtime.Mwe2Launcher - org.eclipse.xtext.naming.QualifiedName.create(Ljava/lang/String;)Lorg/eclipse/xtext/naming/QualifiedName;
java.lang.NoSuchMethodError: org.eclipse.xtext.naming.QualifiedName.create(Ljava/lang/String;)Lorg/eclipse/xtext/naming/QualifiedName;
at org.eclipse.emf.mwe2.language.scoping.InjectableFeatureLookup.collectFeatures(InjectableFeatureLookup.java:52)
at org.eclipse.emf.mwe2.language.scoping.InjectableFeatureLookup.collectFeatures(InjectableFeatureLookup.java:41)
at org.eclipse.emf.mwe2.language.scoping.InjectableFeatureLookup.getInjectableFeatures(InjectableFeatureLookup.java:30)
at org.eclipse.emf.mwe2.language.scoping.Mwe2ScopeProvider.createComponentFeaturesScope(Mwe2ScopeProvider.java:132)
at org.eclipse.emf.mwe2.language.scoping.Mwe2ScopeProvider.scope_Assignment_feature(Mwe2ScopeProvider.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.eclipse.xtext.util.PolymorphicDispatcher.invoke(PolymorphicDispatcher.java:291)
at org.eclipse.xtext.scoping.impl.AbstractDeclarativeScopeProvider.polymorphicFindScopeForReferenceName(AbstractDeclarativeScopeProvider.java:150)
at org.eclipse.xtext.scoping.impl.AbstractDeclarativeScopeProvider.getScope(AbstractDeclarativeScopeProvider.java:98)
at org.eclipse.xtext.linking.impl.DefaultLinkingService.getScope(DefaultLinkingService.java:59)
at org.eclipse.xtext.linking.impl.DefaultLinkingService.getLinkedObjects(DefaultLinkingService.java:119)
at org.eclipse.xtext.linking.lazy.LazyLinkingResource.getEObject(LazyLinkingResource.java:179)
at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(ResourceSetImpl.java:223)
at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:197)
at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:257)
at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eResolveProxy(BasicEObjectImpl.java:1473)
at org.eclipse.emf.mwe2.language.mwe2.impl.AssignmentImpl.getFeature(AssignmentImpl.java:111)
at org.eclipse.emf.mwe2.language.mwe2.impl.AssignmentImpl.eGet(AssignmentImpl.java:229)
at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1011)
at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eGet(BasicEObjectImpl.java:1003)
at org.eclipse.emf.ecore.util.EContentsEList$FeatureIteratorImpl.hasNext(EContentsEList.java:403)
at org.eclipse.emf.ecore.util.EcoreUtil.resolveCrossReferences(EcoreUtil.java:302)
at org.eclipse.emf.ecore.util.EcoreUtil.resolveAll(EcoreUtil.java:296)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:86)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:62)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Runner.run(Mwe2Runner.java:52)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Launcher.run(Mwe2Launcher.java:74)
at org.eclipse.emf.mwe2.launch.runtime.Mwe2Launcher.main(Mwe2Launcher.java:35)
Ștefan
[Updated on: Tue, 22 May 2012 12:38] Report message to a moderator |
|
|
| Re: J2SE-1.7 Problem [message #875442 is a reply to message #874982] |
Tue, 22 May 2012 19:07  |
|
Hi,
you can configure the Java Version in the MANIFEST.MF files of the projects. Feels free to change J2SE-1.5 to JavaSE-1.7.
The Discouraged Access warning says that you are using API that is not public (by meaning of eclipse APIs)
and thus can be changed. as long as this happens in generated classes feel free to ignore the message.
to the exception you get: what do i have to do to reproduce the problem?
~Christian
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
| Re: J2SE-1.7 Problem [message #875869 is a reply to message #875442] |
Wed, 23 May 2012 13:31 |
Ștefan Săftescu
Messages: 4
Registered: May 2012 |
Junior Member |
|
|
I get that exception on a new project or on any of the example projects, so there's nothing in particular you need to do to reproduce it.
I run Arch Linux with openjdk7.b147 and a standard Java Eclipse with CDT added on as well as Xtext.
When I installed Xtext, I might have skipped the Maven integration package because it had some dependencies I didn't care to resolve. However, I wouldn't expect that to affect the simplest of projects (otherwise it would have been a requirement of Xtext).
Anyway, let me know what you think and what kind of information I could provide you with.
Ștefan
[Updated on: Wed, 23 May 2012 13:32] Report message to a moderator |
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02648 seconds
] 
Search
Help
Register
Login
Home
