Eclipse Community Forums: Sirius » Warning: The EClass XXX used in domainClass is not accessible

Help

Home

Home » Eclipse Projects » Sirius » Warning: The EClass XXX used in domainClass is not accessible

Show: Today's Messages :: Show Polls :: Message Navigator

Warning: The EClass XXX used in domainClass is not accessible [message #1786930]

Wed, 16 May 2018 02:03

Adalberto Jr

Messages: 36
Registered: December 2017

Member

Hi.

What does this warning message mean?

"The EClass XXX used in domainClass is not accessible. You are most likely trying to use an EClass without having a dependency to its plugin."

How can I solve it?

Regards.

Report message to a moderator

Re: Warning: The EClass XXX used in domainClass is not accessible [message #1786946 is a reply to message #1786930]

Wed, 16 May 2018 08:00

Pierre-Charles David

Messages: 703
Registered: July 2009

Senior Member

As mentioned in the error message, the plugin containing your modeler definition must have a dependency towards the plug-in which defines your metamodel.

Pierre-Charles David - Obeo

Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius

Report message to a moderator

Re: Warning: The EClass XXX used in domainClass is not accessible [message #1786962 is a reply to message #1786946]

Wed, 16 May 2018 12:56

Adalberto Jr

Messages: 36
Registered: December 2017

Member

Pierre,

the strange thing is that my project was working fine. I was trying to integrate it with an Acceleo project. Suddenly, this message appears.

Where I must look to fix this error?

Regards

Report message to a moderator

Re: Warning: The EClass XXX used in domainClass is not accessible [message #1786964 is a reply to message #1786962]

Wed, 16 May 2018 14:26

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

When you edit a Sirius diagram or an Acceleo transformation you are running within Eclipse and everything registered in your Eclipse workspace can be accessible.

When you run an Acceleo transformation you are running a standalone Java application with some help from Eclipse in that the classpath is auto-generated from the MANIFEST.MF; it uses only what is registered in the MANIFEST.MF. Therefore fix your classpath, by adding a MANIFEST.MF dependency to what you need. That should fix it for simple file layouts. If you have a complex workspace spread across many GIT locations, you could be in trouble.

Regards

Ed Willink

Report message to a moderator

Previous Topic:	Some Validation Rules are not executed properly within the generated plugin.
Next Topic:	The feature 'activatedLayers' has a reference to '' which cannot be f

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 05:58:58 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter