Donát Csikós
Donát Csikós
Thanks, @CsCherrYY for the contribution!
You can set the XDG_CACHE_HOME environmental variable for Eclipse to move the versions.json file to a better location.
I had a quick look at how m2e achieves the intended behavior. It defines a custom runtime classpath provider who sets the classpath for the tests in the order explained...
We didn't implement this because we want to minimize the difference between Gradle executions started from the IDE and the command line. Users can specify the Java home in the...
We are one step closer. You can configure a custom Java home in the Gradle preferences.
I can reproduce the issue, even with Gradle 5.5.1. Most probably it's a bug in the `eclipse-wtp` plugin
With the simple workaround available (running synchronization twice) we can indeed treat this as low prio.
You can do the workaround in the `eclipse.classpath.file.whenMerged` block as well.
In the `ear` project, you probably need to add the `deploy` dependency scope to `eclipse.classpath.plusConfigurations`.
You can find a couple of examples here: https://discuss.gradle.org/t/buildship-1-0-18-is-now-available/19012 At the same time, the solution with `eclipse.classpath.plusConfigurations` is more preferable imho.