Eclipse Community Forums: M2T (model-to-text transformation) » [Acceleo3] Meta model in separate project

Home » Modeling » M2T (model-to-text transformation) » [Acceleo3] Meta model in separate project

[Acceleo3] Meta model in separate project [message #662658]

Thu, 31 March 2011 08:59

Eclipse User

Hi,

I've created two projects, one holding the meta model and one holding the templates. Do I have to make some special settings in the 'templates' project in order to recognize (and remember) that the meta model origins from a different project?

I'm regularly confronted with errors stating that the meta model can not be resolved. I'm referring to the meta model using its Ns uri. QVT's meta model explorer shows that the model is present in the workspace.

Might this be caused by the fact that I'm using a dynamic metamodel?

Greetings,
Wilbert.

[Updated on: Thu, 31 March 2011 08:59] by Moderator

Re: [Acceleo3] Meta model in separate project [message #663157 is a reply to message #662658]

Mon, 04 April 2011 03:20

Eclipse User

Hi,

The problem may be coming from the use of a dynamic metamodel. We have a known bug with dynamic metamodel: https://bugs.eclipse.org/bugs/show_bug.cgi?id=337011

Stephane Begaudeau, Obeo
--
Twitter: @sbegaudeau
Acceleo wiki: http://wiki.eclipse.org/Acceleo
Blogs: http://stephanebegaudeau.tumblr.com & http://sbegaudeau.tumblr.com

Re: [Acceleo3] Meta model in separate project [message #663466 is a reply to message #663157]

Tue, 05 April 2011 04:44

Eclipse User

Hi,

I think it is related with a dynamic metamodel. The symptoms (unrecognized model elements) also occurs in my case.

Greetings,
Wilbert.

Previous Topic:	[XPand2] Unknown type 'ecore::EClass'
Next Topic:	[Xtext2] Extending Xbase expressions

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 19:00:49 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter