Gradle "includeBuild" no longer recognizes imported classes in the IDE

When utilizing "includeBuild" in the settings.gradle file, the IDE no longer recognizes java imports/objects from the included project. Compiling in gradle via the command line continues to work as expected.

Environment

• Operating System: Windows
• JDK version: 1.8/17
• Visual Studio Code version: 1.88.1
• Java extension version: 1.29

Steps To Reproduce

1. Run gradle init to generate a java library called 'inc1'
2. Run gradle init to generate a java library called 'inc2'
3. Add 'group="inc2"' to inc2 build.gradle
4. Add includeBuild '..\\inc2' to the inc1 settings.gradle file
5. Add implementation "inc2:lib:1.0.0" to inc1 build.gradle dependencies
6. Create class Lib2.java in the inc2 project
7. Import and instantiate the Lib2 object in the inc1 project
8. Run gradle assemble in inc1 and verify success
9. Open inc1 in VSCode and verify it can not locate the Lib2 object

[Sample Project]

Current Result

The Lib2 import cannot be resolved in VSCode

Expected Result

The Lib2 import can be resolved in VSCode

Additional Informations

Inizia con il progetto di esempio collegato e riproduci il problema usando inc1/settings.gradle, inc1/build.gradle e il progetto inc2 incluso; confronta l’output riuscito di gradle assemble con l’import di Lib2.java non risolto da VS Code. Traccia la gestione della dipendenza includeBuild da parte dell’estensione Java e considera il problema completato quando l’import di Lib2 viene risolto in VS Code mentre la build Gradle continua ad avere esito positivo.