Can't resolve imports when using includeBuild in package with v3.13.0 #1435
Description
Extension Name: vscode-gradle
Extension Version: v3.13.0
OS Version: macOS 13.6
VSCode version: v1.83.1
Describe the bug
Java imports of local packages can't be resolved when using the includeBuild feature in a gradle.settings file. This only occurs with vscode-gradle v3.13.0. Going back to v3.13.7 resolves the problems.
To Reproduce
I've created a repository that reproduces the problem here:
https://github.com/jjavery/vscode-gradle-includebuild-bug
Open vscode-gradle-includebuild-bug.code-workspace in VSCode, wait for the Java build, and observe the errors in the PROBLEMS panel.
Expected behavior
Expect to be able to use includeBuild to define a composite build of packages in a VSCode workspace.
Screenshots
Output from "Gradle for Java"
[info] [gradle-server] Server started, listening on 52758
[info] Gradle client connected to server
[info] Java Home: /opt/homebrew/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
[info] JVM Args: --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,-XX:MaxMetaspaceSize=384m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant
[info] Gradle User Home: ~/.gradle
[info] Gradle Version: 8.3
[info] Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
CONFIGURE SUCCESSFUL in 4s
[info] Java Home: /opt/homebrew/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
[info] JVM Args: --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,-XX:MaxMetaspaceSize=384m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant
[info] Gradle User Home: ~/.gradle
[info] Gradle Version: 8.3
[info] Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.3/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
CONFIGURE SUCCESSFUL in 651ms
[info] Found 76 tasks
[info] Build file opened: vscode-gradle-includebuild-bug/package-1/build.gradle
[info] Build file opened: vscode-gradle-includebuild-bug/package-1/settings.gradle
[info] Build file opened: vscode-gradle-includebuild-bug/package-1/build.gradle
[info] Build file opened: vscode-gradle-includebuild-bug/package-1/settings.gradle
Does the bug still exist if you disable all other extensions?
Yes, although I didn't try it without Language Support for Java v1.23.0
Additional context
Unsure if relevant but all of my testing has been with a VSCode workspace. Each package is it's own folder in a single workspace.