Please can I ask if it is intended that the VSCode Java Maven integration is expected to integrate with a projects maven-surefire-plugin configuration?

[tomjenkinson]

For example, system property variables https://maven.apache.org/surefire/maven-surefire-plugin/examples/system-properties.html#systemPropertyVariables.

If it's not intended to work and if one wanted to raise a feature request to try to get it to work, then please can I ask if the appropriate method to request such a feature would be via raising an issue in the GitHub Issues of this project?

[ebullient]

Perhaps a better discussion here: https://github.com/microsoft/vscode-java-test

See especially: https://github.com/Microsoft/vscode-java-test/wiki/Run-with-Configuration

[tomjenkinson]

Thank you very much for the input!

I don't spot a place for discussions to take place in that (microsoft/vscode-java-test) repo and also, I think that the Maven integration is more relevant to this (redhat-developer/vscode-java) repo? But should the Maven integration not automatically populate the test configuration, then what you have pointed at definitely seems useful when trying to find an alternative approach.

I had happened to already use a workaround like that to get one of the more simpler "complex" tests integrated (basically a single property to allow a Byteman test to work by setting a system property to allow the JDK to attach to self) but for some tests there could be a lot of properties to copy around and traversing the poms looking for the right properties to copy in and keep aligned with the pom.xml(s) could be challenging?

Thank you again for the input, and from over in that repo I have found: microsoft/vscode-java-test#1233 - which is broadly what I am seeing too.

[ebullient]

Feels like that issue should be reopened, given you can provide additional information (which was missing).

[tomjenkinson]

Thanks Erin, I don't think I have the ability to re-open the issue myself but I did add a comment.

[tomjenkinson]

I think if it's not expected to work, the feature request would be something like:

Extend Language support for Java ™ for Visual Studio Code Maven integration to allow configuring the VSCode test executor in Maven specific ways

In particular:

• Allow the VSCode test executor to automatically be configured with properties specified in maven-surefire-plugin configuration for the module
• Allow the VSCode test executor classpath to be aware of dependencies specified by profiles