The Sculptordsl Editor incorrectly reports "Imported resource could not be found." errors

48 views
Skip to first unread message

zhongw...@hotmail.com

unread,
Dec 20, 2013, 2:29:00 AM12/20/13
to sculptor...@googlegroups.com

After I imported the sculptor-shipping example project into Eclipse workspace, the Sculptordsl Editor incorrectly reports "Imported resource could not be found." errors on 'import "classpath:/xxxx.btdesign"' lines. I think the problem is caused by dsl validations.

Is there anybody have the same problem? And how to solve the problem?


Torsten Juergeleit

unread,
Dec 20, 2013, 5:12:12 AM12/20/13
to sculptor...@googlegroups.com
> Is there anybody have the same problem?

Yes, unluckily currently everyone (who's using the m2e plugin) runs into the same issue :-(

This is due to the m2e Eclipse plugins configuration of the projects source folders. The plugin disables copying Maven resources (e.g. from "main/java/resources/*") to "target/" (via an exclusion pattern in the resource-related source folders). Therefore the imported model file isn't copied to "target/" and isn't available on the projects classpath (and "invisible" for Sculptors EMF-based meta model). This issue is tracked in #25.

Maybe we have to come up with our own full-blown Xtext scope implementation which adds Mavens resource folders to EMFs internal resource repository.
Still investigating...

/Torsten
Reply all
Reply to author
Forward
0 new messages