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.

Reproduce el problema con el proyecto spring-petclinic: selecciona Gradle, ejecuta ./gradlew build, inicia el proyecto e inspecciona el argfile. Rastrea el manejo del classpath que añade las carpetas bin y build; se considera terminado cuando la carpeta build está ausente del classpath generado y ya no se produce la inicialización duplicada de la base de datos.