Community
Participate
Working Groups
In the past I could refer to any elements from ecore using the prefix 'ecore'. But since 1.0.0 the tooling adds marker to such type references: Example: -----Test.ext ------- import ecore; main(EClassifier c) : c.eClass(); -------------------------- Fehler : couldn't find operation 'eClass()' for type 'ecore::EClassifier' -----Test.ext ------- import ecore; main(EClassifier p) : ((EObject) p).eClass(); -------------------------- Fehler : cannot cast from ecore::EClassifier to ecore::EObject
There are no problems running the example in my workspace eclipse. But the target eclipse is using emf 2.5 but Helios is using 2.6. Maybe we should also upgrade the targeteclipse to emf 2.6?
Yes, maybe it's the new EMF. I am using a Helios Classic with Xtext and Xpand SDK installed. The org.eclipse.xtend.util.stdlib project shows a couple of errors, which all seem to go down to this problem.
Ok, I will wait for an update of the targeteclipse up to Helios and emf 2.6 bevore I take a further look at this bug, ok?
(In reply to comment #3) > Ok, I will wait for an update of the targeteclipse up to Helios and emf 2.6 > bevore I take a further look at this bug, ok? It is unlikely that we'll change the target platform to Helios / EMF 2.6
would you please tell me the status of this bug? Is it resolved yet?
I used Eclipse 3.6, EMF 2.6, mdt-xpand-sdk-1.0.1, EMFMetaModel is used It seems that xtend script cannot recognize EObject: - using "import ecore": NOT OK - using "ecore::EObject": NOT OK - class cast from EObject derived obj -> EObject: NOT OK
upgrade to mdt-xpand-sdk-1.1.0, still got this bug
It's not been solved yet.
Hi Sven Efftinge, Have you had plan to resolve this bug yet? It's my appreciated if you can provide me the patch soon.
This is a batch close of open M2T Xpand bugs. It is not planned work on this component in the foreseeable future. If you think this issue needs to be solved and you plan to contribute a fix then feel free to reopen it.