Address the deprecation of AbstractJavaLaunchConfigurationDelegate getClasspath(ILaunchConfiguration)

[cdietrich]

JDT wants to deprecate org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getClasspath(ILaunchConfiguration)

we should address this.

we also should investigate what of customization is still needed at all

(affects mwe and mwe2)

[cdietrich]

@szarnekow this is the mwe jdt deprecation issue

[cdietrich]

https://bugs.eclipse.org/bugs/show_bug.cgi?id=529435

[szarnekow]

I'd resort to reflection: use getClasspathAndModulepath, if available, fallback to getClasspath otherwise. Assign the module path and the classpath from the two dimensional result array to the VM runner config. What do you think, @cdietrich ?

[cdietrich]

sounds feasible. the downside would be that we would no longer recognize if they change it again.
as there is no direct build against "latest platform"

[szarnekow]

I prefer raising the lower bound for JDT and use getClasspathAndModulePath

[cdietrich]

the problem is that we set the min mwe version in xtext.sdk
so that wont work with Xtext + MWE (latest) + Oxygen3a

[cdietrich]

of course we could keep the old runtime dep and use a newer target platform.
and hope we dont do programming errors
as we do it for xtext-core and extras

[cdietrich]

we had a closer look.
new method is already there in 3a although marked as @since 3.10 whereas Oxygen3a as 3.9.100

[cdietrich]

=> we can use the new method only

[cdietrich]

or

		// Bug 529435 :to move to getClasspathAndModulepath after java 8 is sunset
		VMRunnerConfiguration runConfig = new VMRunnerConfiguration(mainTypeName, getClasspath(configuration));

[cdietrich]

we also should investigate what of customization is still needed at all

[cdietrich]

moved to 2.11.3