Eclipse Community Forums: M2T (model-to-text transformation) » Analyzing accessible EMF metamodels for project

Home » Modeling » M2T (model-to-text transformation) » Analyzing accessible EMF metamodels for project

Analyzing accessible EMF metamodels for project [message #656806]

Mon, 28 February 2011 12:00

Eclipse User

Hello experts,

Any time I added a new component to my project I keep getting the following message :

"Analyzing accessible EMF metamodels for project ..."

What does that mean and how to get rid of that ?

Thanks,

Re: Analyzing accessible EMF metamodels for project [message #657320 is a reply to message #656806]

Wed, 02 March 2011 07:48

Eclipse User

All projects having the Xtend/Xpand nature will be scanned for referencing EMF based metamodels and metadata is collected for them to know the existing types and their features.

It should be possible to disable this by removing the Xtend nature (Configure from context menu) for a project.

The plugin responsible for this is org.eclipse.xtend.typesystem.emf.ui.

~Karsten

Re: Analyzing accessible EMF metamodels for project [message #1429682 is a reply to message #657320]

Tue, 23 September 2014 11:32

Eclipse User

Another option is to disable "Xtend/Xpand -> EMF Metamodels" in preference or in project property. This metamodel contributer is required only when .ecore models needs to be accessed from Xpand scripts.

- Nirmal

Previous Topic:	code generation for object c
Next Topic:	org.eclipse.acceleo.engine.AcceleoEvaluationException: The type of the first parameter of the main t

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Apr 23 18:48:37 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter