-
Notifications
You must be signed in to change notification settings - Fork 26
Build problems with xcore and xtext-maven-plugin:2.17.0.M2 #71
Comments
you should keep to the old emf/xcore versions the bom wants to have. |
and use java 8 for that. |
I guess I'll have to wait on 2.17.0 release, as the older versions suddenly started failing with an error:
as covered by eclipse/xtext#1373, which ended up closed with the advice 'use a newer version'. |
no this wont help. M2 has everything we plan |
if you basically list everything you want explicitely and dont pull |
you you just use xcore maven will pull arbitry combinations cause |
can you provide a minimal sample project sowing the problem? |
Reproduction test case: The model needs to have a bit of stuff in it to cause some generic type reasoning to happen. I want to specify everything; I just have no idea what combination of versions of the 56 jar files involved would successfully compile against each other. |
i dont get it running neither . the iterable import in the xcore file looks bugus.
is this the message you get? |
https://github.com/cdietrich/xcore-maven-example works with 2.16 |
scope.getAllElements() => is it possible Iterable is simply not allowed in an op e.g.
|
import org.eclipse.xtext.common.types.Iterable |
=> working combinations at wonder if you can transfer to your problem |
Note that the name referenced in the op's return type must refer to an EClassifier in some Ecore model. So while many things are visible because Ecore has EDataTypes for them and the scoping rules make those visible, don't expect some arbitrary Java class name to be visible in this scope. One must define a type in some Xcore model to make Iterable visible as the return type of an op or as the type of any of its parameters. E.g., like this: type Iterable wraps Iterable class Test { |
Oops, it should be like this with a type parameter so that you can pass arguments and so there is no raw type warning.
|
Hmm, every time the < T > disappears when I post Iterable < T >when I post! |
Following the link above and copying out the exact full list of dependencies to the dependency section of the maven-plugin does seem to work. |
TODO: can we improve something or just close |
Might as well close this specific issue. But please keep in mind that there is obviously some kind of underlying process or tools issue that causes these kind of dependency problems to keep happening. |
Not sure if this is the right place to raise this, as it is a typical eclipse dependency interaction where it is impossible, as a user, to find the root cause.
Building a dsl with xcore, xtext-maven-plugin and the xtext-dev-bom, get
This comes from a call in
XcoreJvmInferrer
oforg.eclipse.emf.ecore.xcore
1.7.0 toEcoreValidator.EGenericTypeBuilder.INSTANCE.buildEGenericType
, which does not exist untilorg.eclipse.emf.ecore
2.16.0.Relevant classpath entries during the build are:
The version 2.12.0 of
org.eclipse.emf.common
is specified byxtext-dev-bom
2.17.0.M2
.The only other publicly available version of
org.eclipse.emf.ecore.xcore
that I can find is 1.3.1, which fails with a different error.Full stack is:
Thread [main] (Suspended (exception NoSuchMethodError))
owns: Object (id=32182)
XcoreJvmInferrer$TypeReferenceHelper.getEGenericType(String) line: 2679
XcoreJvmInferrer.getJvmTypeReference(String, EObject) line: 2736
XcoreJvmInferrer$10.inferStructure() line: 1618
XcoreJvmInferrer$10.inferStructure() line: 1
XcoreJvmInferrer$10(XcoreJvmInferrer$JvmElementInferrer).(int) line: 148
XcoreJvmInferrer$10.(XcoreJvmInferrer, int, GenEnum) line: 1612
XcoreJvmInferrer.getDeclaredType(GenEnum) line: 1612
XcoreJvmInferrer.getDeclaredTypes(GenClassifier) line: 1602
XcoreJvmInferrer.getDeclaredTypes(GenPackage) line: 1004
XcoreJvmInferrer.inferElements(GenModel) line: 218
XcoreModelAssociator.installDerivedState(DerivedStateAwareResource, boolean) line: 97
XcoreResource(DerivedStateAwareResource).installDerivedState(boolean) line: 243
XcoreResourceDescriptionManager(DerivedStateAwareResourceDescriptionManager).internalGetResourceDescription(Resource, IDefaultResourceDescriptionStrategy) line: 54
The text was updated successfully, but these errors were encountered: