microsoft / vscode-gradle

Manage Gradle Projects, run Gradle tasks and provide better Gradle file authoring experience in VS Code
https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-gradle
MIT License
124 stars 51 forks source link

Tasks not listed if Gradle sub-project opened in project's directory #1478

Open Franziskus1988 opened 6 months ago

Franziskus1988 commented 6 months ago

Extension Name: vscode-gradle Extension Version: v3.13.5 OS Version: Windows 23H2 VSCode version: 1.87.2 Java version: openjdk 17.0.8.1 2023-08-22 LTS Gradle version: 7.6.2 (local version)

Describe the bug When I open the root dir of my Gradle project all tasks are shown correctly for every sub-project. If I open a sub-project itself with VSCode not all tasks of the project are shown. Instead, it seems that a subset of the tasks of the root project is shown.

Expected behavior I would expect that when opening a Gradle sub-project directly that the same tasks are shown as when opening the root project.

Screenshots Example project as shown in root project:

image

Same project opened in folder of project:

image

Output from "Gradle for Java" [debug] [gradle-server] Starting server [debug] [gradle-server] Gradle Server cmd: c:\Users\310305543.vscode\extensions\vscjava.vscode-gradle-3.13.5\lib\gradle-server.bat 54176 [info] [gradle-server] Server started, listening on 54176 [info] Gradle client connected to server [debug] Refreshing tasks [info] Java Home: E:\project\jdk64 [info] JVM Args: -XX:MaxMetaspaceSize=2048m,-XX:+HeapDumpOnOutOfMemoryError,--add-opens=java.base/java.io=ALL-UNNAMED,--add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-Xms1000m,-Xmx2500m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant [info] Gradle User Home: E:\gradle\vscode\.gradle [info] Gradle Version: 7.6.2 ..... CONFIGURE SUCCESSFUL in 35s 48 actionable tasks: 20 executed, 28 up-to-date [info] Found 48 tasks

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

Additional context

{
  "gradle.nestedProjects": true,
  "java.configuration.detectJdksAtStart": false,
  "java.configuration.runtimes": [
    {
      "default": true,
      "name": "JavaSE-17",
      "path": "E:/project/jdk64"
    }
  ],
  "java.dependency.packagePresentation": "hierarchical",
  "java.import.generatesMetadataFilesAtProjectRoot": false,
  "java.import.gradle.enabled": false,
  "java.import.gradle.home": "E:/project/gradle",
  "java.import.gradle.java.home": "E:/project/jdk64",
  "java.import.gradle.user.home": "E:/gradle/vscode/.gradle",
  "java.import.gradle.wrapper.enabled": false
}