Eclipse Community Forums: TMF (Xtext) » Referencing plug-in resources

Help

Home

Home » Modeling » TMF (Xtext) » Referencing plug-in resources

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

Referencing plug-in resources [message #1059074]

Thu, 16 May 2013 14:25

Roland S.

Messages: 36
Registered: September 2009

Member

Hi,

we developed a DSL with Xtext and created a product that ships with some documents in that language in a plug-in. If we turn on the pack flag so that the shipped plug-in is put into a jar file, we can add a dependency to that plug-in and reference elements inside the shipped documents. If the plug-in is unpacked after installation (the files are inside a folder in the plugins folder instead of a jar file), referencing the same elements does not work.

Do you have any hints how to avoid this limitation? Sadly we need to unpack some of the plug-ins.

Regards,
Roland

Report message to a moderator

Re: Referencing plug-in resources [message #1059713 is a reply to message #1059074]

Tue, 21 May 2013 10:28

Roland S.

Messages: 36
Registered: September 2009

Member

I found the reason for this behaviour. In the JdtToBeBuiltComputer:123 it is checked, whether a project shall be processed and the resources inside the project be parsed. This is done by searching for a Xtext nature (XtextProjectHelper.hasNature(otherProject)). Since the delivered project is mapped to a fake workspace location (.org.eclipse.jdt.core.external.folders) and does not provide any natures, the resources in the project are not analyzed. My quickfix is to bind a custom JdtToBeBuiltComputer which provides the desired functionality. Maybe this should be integrated into the JdtToBeBuiltComputer class in future versions?!?

Report message to a moderator

Previous Topic:	Xtext Save
Next Topic:	Change EMFResource

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 23:43:28 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter