should not include test classes in classpaths when auto resolve maven project

[testforstephen]

Original notes from @claycephas ,
#108 (comment)

Current implementation just invoked JavaRuntime.computeDefaultRuntimeClassPath(javaProject), the result is not accurate. Need fix these two issues:

1. When debugging a maven-based project with VS Code, it is including test classes in the classpaths.

2. For maven project with multiple modules, the auto-generated classpaths by the debugger didn't contain the depended modules' classpaths.

[supersonicclay]

Some potential places to look:

• https://github.com/Microsoft/java-debug/blob/master/com.microsoft.java.debug.plugin/src/main/java/com/microsoft/java/debug/plugin/internal/ResolveClasspathsHandler.java
• https://github.com/eclipse/eclipse.jdt.debug/blob/fce60cee0f2525cbeeb808581833fbaa9deaa449/org.eclipse.jdt.launching/launching/org/eclipse/jdt/launching/JavaRuntime.java

[supersonicclay]

Is there a way to make this conditional so that some launch configurations include the test classes and some don't? I'm thinking we would want to support debugging the implementation code (without tests) or debugging unit tests (which should include tests).

[testforstephen]

We'll add special support for JUnit. See task #76

[gorkem]

I think @fbricon has adopted JDT.LS and m2e to exclude test classes.

[yaohaizh]

Close this as the LS filtered test classes.

[supersonicclay]

@yaohaizh I'm still seeing /myproject/target/test-classes listed in the classpaths with redhat.java@0.21.0 and vscjava.vscode-java-debug@0.7.0.

[yaohaizh]

Need further verify this issue.

[andxu]

The bug is still unfixed: