Jinbo Wang

Here is the document about lightweight mode. https://code.visualstudio.com/docs/java/java-project#_lightweight-mode

Tried multiple maven projects using generate-source plugins, some of them are recognized well by vscode-java, some not. **generate-source is not recognized:** antlr3-maven-plugin sample: https://github.com/antlr/stringtemplate4 **generate-source is automatically added to .classpath:**...

I see. The current m2e leverages lifecycle-mapping-metadata to recognize the customized generate-sources goal from the maven plugin. Here is a [wiki](https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html#metadata-source-lookup-order) about how m2e lookup the lifecycle mapping from different...

vscode-java-pack extension will use jcmd to check whether the language server process is alive. Since jcmd is a built-in command tool from JDK distribution, we might need to report it...

> @testforstephen , you mentioned there's already an issue, or PR for this that's incoming ? I wasn't able to find any issue on the vscode-java-debug end. @rgrunber I tried...

The message id doesn't exist in package.nls.json.  > let me know if this works for you now. I think the last thing to test is specifically how it interacts...

1) If .vscode/launch.json doesn't exist in your workspace, you could click the link "**create a launch.json file**" and Java Debugger will create a initial launch.json file with some base configuration...

If you're talking about how to add environment variables, the `env` is exactly for that. Could you pls share your launch.json configuration?

Duplicated with https://github.com/redhat-developer/vscode-java/issues/996 The "Building" message you saw in the status panel is just a fake message, not representing a compilation operation.

> Java extension version: 0.64.1 Your Java extension version is a little old, could you update all Java extensions to the latest version and try again? AFAIK, the side Java...