Comment 1 Martin Taal 2013-12-12 08:36:40 EST

Build and published

Comment 2 Martin Taal 2013-12-12 08:59:55 EST

More feedback/test

Comment 3 Dominik Leszyk 2013-12-12 11:59:35 EST

(In reply to Martin Taal from comment #2)
> More feedback/test

Tried with build 0.1.0.v201312121235 but no luck. 

<code>
java.lang.IllegalStateException: Invalid EPackage: profile
Diagnosis of platform:/resource/org.sample.profile/model/profile.ecore#/
The feature 'eType' of 'platform:/resource/org.sample.profile/model/profile.ecore#//ProfileEntry/userId' contains an unresolved proxy 'platform:/resource/org.eclipse.emf.ecore/model/Ecore.ecore#//EString'
The feature 'eAttributeType' of 'platform:/resource/org.sample.profile/model/profile.ecore#//ProfileEntry/userId' contains an unresolved proxy 'platform:/resource/org.eclipse.emf.ecore/model/Ecore.ecore#//EString'
The feature 'eRawType' of 'platform:/resource/org.sample.profile/model/profile.ecore#//ProfileEntry/userId/@eGenericType' contains an unresolved proxy 'platform:/resource/org.eclipse.emf.ecore/model/Ecore.ecore#//EString'
The feature 'eClassifier' of 'platform:/resource/org.sample.profile/model/profile.ecore#//ProfileEntry/userId/@eGenericType' contains an unresolved proxy 'platform:/resource/org.eclipse.emf.ecore/model/Ecore.ecore#//EString'
</code>

Comment 4 Moritz Höser 2014-04-09 12:09:34 EDT

I tried it with 1.2.0.v20140407-1043.

When generating the .ecore file via genmodel from .xcore, the eCore type is not correctly resolved:

eType="ecore:EDataType ../../org.eclipse.emf.ecore/model/Ecore.ecore#//EString"

Can you have a second look?

Comment 5 Martin Taal 2014-12-27 19:01:33 EST

Hi,
I did a new build with several fixes and new feature (XCore integration). Can you retry it with this build?

http://download.eclipse.org/modeling/emft/texo/updates/interim/

gr. Martin

Comment 6 Rainer Menke 2015-01-26 20:16:51 EST

Hi Martin,

do you think the assignment to Texo is correct? Currently I am not using texo, but the generation of ecore from xcore with using org.eclipse.emf.ecore.xcore.sdk.feature.group ( 1.2.1v20141013-0331 ). If I modell in xcore 

	@ExtendedMetaData(kind="attribute", name="theme" )
	unique org.eclipse.emf.ecore.xml.^type.String theme

I get 

    <eStructuralFeatures xsi:type="ecore:EAttribute" name="theme" eType="ecore:EDataType ../../org.eclipse.emf.ecore/model/Ecore.ecore#//EString">
      <eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
        <details key="kind" value="attribute"/>
        <details key="name" value="theme"/>
      </eAnnotations>
    </eStructuralFeatures>

instead of the expected

    <eStructuralFeatures xsi:type="ecore:EAttribute" name="theme" eType="ecore:EDataType http://www.eclipse.org/emf/2003/XMLType#//String">
      <eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
        <details key="kind" value="attribute"/>
        <details key="name" value="theme"/>
      </eAnnotations>
    </eStructuralFeatures>

Comment 7 Martin Taal 2015-01-27 12:28:18 EST

Hi Rainer,
Not sure if the assignment to texo is correct. The best is if you can enter a new issue on EMF. So Ed (Merks) can respond on it there.

If you do, it is great if you also list the other issue here.

Thanks!

gr. Martin

Comment 8 Rainer Menke 2015-01-28 05:00:45 EST

Hi Martin,

I generated the bugreport

Bug 458621 - References to Ecore are not resolved correctly when generating code from xcore

Comment 9 Martin Taal 2015-02-16 09:54:58 EST

*** This bug has been marked as a duplicate of bug 458621 ***