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++
The XtextGenerate task currently has a single concept called
classpathwhich serves two purposes:We should split this into
classpathandmodelpathfor two reasonsclasspathdoesn't make any sense for ecosystems like C/C++