Refresh Tasks fails with Gradle 3.5.1 on Ubuntu 18.04 with JDK 1.8

[rizzorc]

Extension Name: vscode-gradle Extension Version: v3.11.0 OS Version: Win 10 20H2 - OS Build 19042.1586 VSCode version: 1.66.2

Describe the bug When opening a folder in VS Code in Ubunto 18.04 (WSL 2.0,) the task list fails to load in vscode even though the running gradlew from the terminal returns a list.

** Output from Gradle ** ~/development/CFW/component-sample$ ./gradlew tasks --all The ProjectDependency.getProjectConfiguration() method has been deprecated and is scheduled to be removed in Gradle 4.0. `ModuleDependency.getConfiguration() has been deprecated and is scheduled to be removed in Gradle 4.0. Use ModuleDependency.getTargetConfiguration() instead.` :tasks ------------------------------------------------------------ All tasks runnable from root project ------------------------------------------------------------ Application tasks ----------------- bootRun - Run the project with support for auto-detecting main class and reloading static resources Build tasks ----------- assemble - Assembles the outputs of this project. sample-client:assemble - Assembles the outputs of this project. .... <long list of tasks > ... BUILD SUCCESSFUL Total time: 2.895 secs

To Reproduce Run the Refresh tasks action

Expected behavior The tasks from the dependencies should appear along with those from the build.gradle

Screenshots

Output from "Gradle for Java" [debug] Refreshing tasks [debug] Get daemon status [info] Java Home: /usr/lib/jvm/adoptopenjdk-8-hotspot-amd64 [info] JVM Args: -XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country,-Duser.language=en,-Duser.variant [info] Gradle User Home: /home/rizzorc/.gradle [info] Gradle Version: 3.5.1 [debug] Get daemon status: Cancelled on client [debug] Get daemon status [info] The ProjectDependency.getProjectConfiguration() method has been deprecated and is scheduled to be removed in Gradle 4.0. ModuleDependency.getConfiguration() has been deprecated and is scheduled to be removed in Gradle 4.0. Use ModuleDependency.getTargetConfiguration() instead.

CONFIGURE SUCCESSFUL

Total time: 3.611 secs [error] [gradle-server] Could not run build action using connection to Gradle distribution 'https://services.gradle.org/distributions/gradle-3.5.1-bin.zip'. [error] Error getting build for /home/rizzorc/development/CFW/component-sample: Could not run build action using connection to Gradle distribution 'https://services.gradle.org/distributions/gradle-3.5.1-bin.zip'. [info] Found 0 tasks

Does the bug still exist if you disable all other extensions? Yes

Additional context See attached txt file for sample build.gradle build.gradle.txt

[CsCherrYY]

What you have seen is the default view, since the extension is trying to get the available tasks, the extension will show this view temporarily and after the exact tasks are available this view will be replaced.

The problem here is why the extension fails to get the tasks. Does your redhat-java extension work well?