Debugger mistakenly included Gradle build folder in classpaths

[akaroml]

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.

[testforstephen]

I couldn't reproduce the issue. Could you share how .classpath file looks like?

F1 -> Java: Open Java Language Server Log File -> Navigate the log directory to find the \redhat.java\jdt_ws\.metadata\.plugins\org.eclipse.core.resources\.projects\spring-petclinic\.classpath

[testforstephen]

I finally reproduced this issue with latest https://github.com/spring-projects/spring-petclinic source code. I observed that Java Projects view also listed the build directory under "Project and External Dependencies" node.

This should be a bug of buildship, where the computed classpath from buildship includes the gradle build directory mistakenly.

// cc: @jdneo @CsCherrYY

[testforstephen]

See spring-projects/spring-petclinic#1213, this seems to be an issue with upstream spring gradle plugin.