Eclipse Community Forums: TMF (Xtext) » Xtext Classpath-Based global scoping

Help

Home

Home » Modeling » TMF (Xtext) » Xtext Classpath-Based global scoping(Classpath-Based scoping without Java and JDT)

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

Xtext Classpath-Based global scoping [message #898961]

Sun, 29 July 2012 15:38

Sandra Shklyaeva

Messages: 16
Registered: July 2012

Junior Member

In the Xtext Documentation I found the following:

"By default Xtext leverages the classpath mechanism since it is well designed and already understood by most of our users. The available tooling provided by JDT and PDE to configure the classpath adds even more value. However, it is just a default: You can reuse the infrastructure without using Java and independent from the JDT."

When I configure classpath-based global scoping as described in the help, the scoping works only if my project is Java Project (has Java Nature and Java Builder).
In other case, it doesn't work.

The questions is how I can reuse the infrastructure (classpath-based global scoping) without using Java and JDT?

Report message to a moderator

Re: Xtext Classpath-Based global scoping [message #898973 is a reply to message #898961]

Sun, 29 July 2012 19:28

Benjamin Schwertfeger

Messages: 53
Registered: July 2009

Member

Hello Sandra,
I am not sure what your intention is. You can not use class paths without java, because the class path is only defined in java and plugin projects. You can use project dependencies in your workspace and references to other model files by changing the container state in your <DSL>UiModule like
public Provider<IAllContainersState> provideIAllContainersState() {
return Access.getWorkspaceProjectsState();
}

If this is not, what you meant, you can explain perhaps.

Regards,
Benjamin

Report message to a moderator

Re: Xtext Classpath-Based global scoping [message #899056 is a reply to message #898961]

Mon, 30 July 2012 11:32

Henrik Lindberg

Messages: 2509
Registered: July 2009

Senior Member

On 2012-29-07 17:38, Sandra Shklyaeva wrote:
> In the Xtext Documentation I found the following:
>
> "By default Xtext leverages the classpath mechanism since it is well
> designed and already understood by most of our users. The available
> tooling provided by JDT and PDE to configure the classpath adds even
> more value. However, it is just a default: You can reuse the
> infrastructure without using Java and independent from the JDT."
>
> When I configure classpath-based global scoping as described in the
> help, the scoping works only if my project is Java Project (has Java
> Nature and Java Builder).
> In other case, it doesn't work.
>

> The questions is how I can reuse the infrastructure (classpath-based
> global scoping) without using Java and JDT?

If you want to look at a project that is using Eclipse Projects and that
sets up depedencies between projects based on meta data in the projects,
you can look at cloudsmith / geppetto @ github. No JDT functionality is
used in Geppetto.
Note that if you package a product that does not include jdt, there are
a couple of other things to also deal with regarding aggregatin of error
markers in the project/package/navigator views. (See the "jdt-ersatz"
stuff in geppetto what is needed).

Regards
- henrik

Report message to a moderator

Previous Topic:	import an Xtext grammar
Next Topic:	Ecore model generation - merge custom and generated java code

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Jun 06 05:39:24 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter