Closed istvanrath closed 12 years ago
We will try to integrate this for 0.6, but depends on error containment.
Pushing back to the future, we don't have time for this in the 0.6 timeframe.
Because of a misconfiguration in the build server @okrosa did not receive an email notification from the build system the he added 3.8/4.2-specific dependencies to the IncQuery runtime project. For now, I fixed it, and hopefully he will also get the repair emails as well. If not, please contact me, and we should fix this.
@bergmanngabor, @istvanrath: these additional dependencies in the incquery.runtime project goes strongly against the possibility to use IncQuery in a plain Java application, as some dependencies (e.g. org.eclipse.core.runtime) also require an Eclipse application running. Please review whether this is ok, or should we look for other possible solutions.
We would eventually want to move this "ClasspathProvider" to an extension, so that the eiq.runtime plugin can stop depending on eclipse.core.runtime and eclipse.core.resources. If running without an Eclipse workspace, we should be able to instantiate the interpreter without customizing its classloader (which is not a big problem, as generated patterns would be used much more frequently in this scenario).
But for now, it looks nice.
The goal is to enable the Xbase interpreter to access components that are included in the classpath of the (host) EMF-IncQuery project.
The components can be imports from the target platform OR references to workspace projects. Both cases should be supported, both at development and runtime.