Alex Boyko

Hmm... Gradle Eclipse Tooling doesn't have support for separate classpath for test and runtime like M2E tools do. It's feature on Gradle Eclipse Integration yet to be implemented.

Try not including “org.gradle.toolingapi.feature”. I’m not sure why it’s there and what it does. The tooliapi plugin project and feature is included into “Gradle IDE” feature and this is probably...

Wonder how you manage to get the "Gradle Tasks" view actions to disappear... I have tried this on Mac OSX and it work fine all the time regardless the real...

We do not support Atom extensions anymore... this problem however is something about JVM not being located where it should be... Is your JVM at this location?

Yes, indeed. It’s on our “ToDo” list for Gradle Eclipse integration. Cheers, Alex On Jun 7, 2014, at 3:13, zyro [email protected] wrote: > the gradle tooling seems to always add...

Turns out that for Java version greater than 8 it should be **Dependencies** tab instead of **Classpath**. JDT launching sets the temp JAR classpath to `false` for "modular" projects (Java...

I'd say 1. is already there. 2. would be nice. 3. There are tags to take advantage of 4. Sorting might come in as part of the Tree View in...

@duduabreu I think the problem is with Eclipse Debug UI rather than STS's plugins... Looks like the problem has been introduced in Eclipse 4.31. Try STS distribution on Eclipse 4.32...

@rwinch IDE should only be setting the env variable for the tests launch, correct? Not for the main boot app execution, right? Wonder if it is necessary to store main...

@rwinch I think I have IDE part ready for testing for the Maven projects. How shall we proceed with letting you to try it? Are you okay trying it from...