Be able to configure in settings JSON files the compiler error/warning/ignore levels

[robmv]

Eclipse allows to configure the JDT compiler error/warning/ignore levels for many options. For example to ignore creating a class that extends an annotation (pretty common on CDI injections *Literal classes).

There is a quick fix:

But that action doesn't add anything to the settings files at any of the User/Workspace/Folder levels and there is no obvious ways to revert the action. Clean Language Server Workspace appear to do it, but it would be useful if all the compiler error level settings, could be individually controlled using VS Code settings files.

[robmv]

I have noticed that if .settings/org.eclipse.jdt.core.prefs is present, for example if the project was imported to an Eclipse workspace and m2eclipse auto generated it, Quick Fix setting are stored there.

The problem with this is that projects imported to Eclipse with m2eclipse, usually have .classpath, .project and .settings added to .gitignore, in order to not have duplicate configuration files (pom.xml and Eclipse ones). For someone still using Eclipse but testing a migration for this extension, this makes things complicated.

In an ideal world, this extension would use its own configuration settings more inline with VS Code conventions. I would love to have all compiler settings on a file on the project much like java.format.settings.url currently works for code formatter settings.

[rgrunber]

"Ignore compiler problem(s)" works as described at #1791 (comment) .

It now respects java.settings.url and will save the options there. If that setting is not defined / file doesn't exist, then the setting will be saved to the project metadata location (it applies the option for every Java project imported). A simple Java: Clean Java Language Server Workspace can be used to clear these out.

As for something like a settings JSON to configure more options :

There is a settings java.settings.url which takes a path to an Eclipse preference file (eg. .vscode/settings.prefs. You can set your preferences in that file (eg. foo=bar). You can place anything from https://github.com/eclipse-jdtls/eclipse.jdt.ls/wiki/Language-Server-Settings-&-Capabilities#java-compiler-options there. See #2358 (comment) as an example.

[robmv]

Thanks @rgrunber. I missed thet java.settings.url could be used for compiler options because it was mentioned on the Java Formatter Options section first and missed it later, my mistake.

I still think that something like:

...
"java.settings": {
  "org.eclipse.jdt.core.compiler.debug.localVariable": .....
}
...

Directly on VS Code files would be nice. Currently there is no UI to build these files, unless you go to Eclipse and export them. If you are using plain VS Code having the settings directly, VS Code can give auto completion, and help directly on the JSON entries, reducing greatly the need to build a custom UI.

[rgrunber]

That's fair. I think The VS Code Java pack provides a UI for the format settings, and I think I had a draft that converted the compiler options to a wizard using https://github.com/redhat-developer/vscode-wizard . Maybe I can look into reviving that.