Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Separate modelpath from classpath #57

Open
oehme opened this issue Jul 13, 2016 · 0 comments
Open

Separate modelpath from classpath #57

oehme opened this issue Jul 13, 2016 · 0 comments

Comments

@oehme
Copy link
Member

oehme commented Jul 13, 2016

The XtextGenerate task currently has a single concept called classpath which serves two purposes:

  • providing JVM types for Xbase
  • providing models for other Xtext languages to link against

We should split this into classpath and modelpath for two reasons

  • most classpath entries don't contain models and should not be indexed. This will be a huge performance gain
  • the term classpath doesn't make any sense for ecosystems like C/C++
@oehme oehme changed the title Separate modelPath from classPath Separate modelpath from classpath Jul 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant