You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Question - Is there an extension point to add arguments to the java command line (like javaagent) #312
In VS Code, testing and debugging are handled by different extensions. And they have different settings to allow customizing the JVM. For example, the Debugger for Java extension has vmArgs exposed so you can manipulate how the JVM is launched when starting an application.
Hope that answers your question. It would be very helpful if you could share more about the use case.
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.
The Ebean Enhancement plugin for other IDEs achieve 'enhancement' by adding a javaagent during the runtime.
To align with that I have implemented an Ebean Enhancement plugin that automatically sets the vmArgs in the launch configuration. In this case the user must select which launch configuration to update.
However, I would like to know if there is a way in which VM arguments can be set at workspace level. That is, not having to have it in each launch configuration in the launch.json. I want to be added and used whenever a launch is triggered for the current workspace in vscode. Just the workspace and not global as well.
Activity
akaroml commentedon Feb 18, 2020
In VS Code, testing and debugging are handled by different extensions. And they have different settings to allow customizing the JVM. For example, the Debugger for Java extension has
vmArgsexposed so you can manipulate how the JVM is launched when starting an application.Hope that answers your question. It would be very helpful if you could share more about the use case.
no-response commentedon Mar 9, 2020
This issue has been closed automatically because it needs more information and has not had recent activity. Please reach out if you have or find the answers we need so that we can investigate further.
Shabirmean commentedon May 11, 2020
The Ebean Enhancement plugin for other IDEs achieve 'enhancement' by adding a javaagent during the runtime.
To align with that I have implemented an Ebean Enhancement plugin that automatically sets the vmArgs in the launch configuration. In this case the user must select which launch configuration to update.
However, I would like to know if there is a way in which VM arguments can be set at workspace level. That is, not having to have it in each launch configuration in the launch.json. I want to be added and used whenever a launch is triggered for the current workspace in vscode. Just the workspace and not global as well.
I have raised this question here: microsoft/vscode#97363 and in SO