Debugger mistakenly included Gradle build folder in classpaths

1. Open spring-petclinic project using VS Code with Java Ext Pack installed
2. When hint to choose between Maven or Gradle, pick Gradle and import the project
3. In terminal, build the project using gradle by ./gradlew build
4. Now launch the project, and inspect the argfile

Both bin and build folders are in the classpath, and it will introduce unexpected consequences.

For example, in the spring-petclinic project, the database initialization script will be executed twice due to the extra classpath entry, resulting in duplicated records in db. This is really hard to troubleshoot and will cause serious confusion.

build folder should not be included in this case.

Riproduci il problema con il progetto spring-petclinic: seleziona Gradle, esegui ./gradlew build, avvia il progetto e ispeziona l'argfile. Traccia la gestione del classpath che aggiunge le cartelle bin e build; il lavoro è completato quando la cartella build è assente dal classpath generato e non si verifica più l'inizializzazione duplicata del database.