Suggestion: Ignore compiler warnings and information from specified directories

[ChrisTrenkamp]

As a user of the vscode-java extension, I would like to ignore Java compiler warnings and information coming from certain directories.

Generated code and unit tests often generate warnings from the compiler. I would like to have warnings coming from certain directories suppressed so it'll be easier to find warnings from code we're interested in.

files.ignore is not good enough because sometimes you want to ignore warnings coming from unit tests. For example, you might want to test your equals() method against different objects, but you will get an information message telling you that it's an unlikely argument.

For now, entering src/main/** into the problems filter seems to be good enough for now, but I would like to create a workspace with some sane defaults for my coworkers to use when pulling the project.

[fbricon]

You can add an ignore_optional_problems flag to your project's .classpath file, like:

<classpathentry kind="src" output="target/classes" path="src/main/java">
    <attributes>
        <attribute name="ignore_optional_problems" value="true" />
    </attributes>
</classpathentry>

[BlazerYang]

same problem, any solution yet?

[ghost]

+1

[dashorst]

Since VS Code no longer generates the .classpath files inside the workspace, it is quite difficult to modify them directly, especially when using a remote devcontainer. Having a UI to add this boolean attribute, or a menu item to open the .classpath file for the project would be absolutely helpful. At this time I can't recommend using VS Code for our project as the number of warnings in generated dwarfs the actual warnings in our code base, and we have a zero warning policy.

[rubensa]

Should be great to have an option to do this in the JAVA PROJECTS view by a right click in an specific source folder (or in the Configure Classpath page).

(related to: #2150)

[rubensa]

Any chance for the ignore_optional_problems to be added for any folder under "target/generated-sources" (like it is currently automatically being added for target/generated-sources/annotations and target/generated-test-sources/test-annotations)?

[heruan]

Any chance for the ignore_optional_problems to be added for any folder under "target/generated-sources" (like it is currently automatically being added for target/generated-sources/annotations and target/generated-test-sources/test-annotations)?

This would be great. I use a Maven plugin to generate a lot of sources in target/generated-sources/** and I have thousands of warnings 🤯

[snjeza]

@rubensa @heruan You can try the ecliseignorehelper plugin.