How can I disable compiler warnings in Eclipse on a file specific basis? [duplicate]

Question

This question already has an answer here:

• Change Eclipse settings to ignore errors on a specific file 7 answers

In my Eclipse project are a handful of generated .java files that I need to use for SQLJ and I can't move to a separate project (due to Administrative Overhead). These files are also regularly regenerated so editing them is unfortunately out.

Unfortunately these files generate a few hundred java compiler warnings which drown out the useful warnings I get on files that I actually can edit.

Is there any way in Eclipse to say Ignore all the warnings of a file-by-file basis? Or can I block out a specific sub-directory?

Answer 1

The "problems" view in eclipse can be filtered; I always have it set to "on selected element and its children only". Granted, this is more of a work-around, but it lessens the impact of having the files in the same project. (Note that even if you must have them in the same project, you can keep them in a separate source folder).

Edit: To configure the filters, find the icon with a downward arrow with tooltip "View Menu" on the top right of the problems view. Click it, and then click "configure contents".

Answer 2

Ensure the files are under the gen folder, the typical home for all generated .java files. Then in the project properties, under Java Build Path, set Ignore optional compile problems for that folder to Yes.

If your project structure requires your files be in a folder other than gen, add that folder to the Java Build Path so that you can enable ignoring optional compile problems for it.

Answer 3

@SuppressWarning annotation?

Per, Stephen's comment, you can find the "Per project compiler settings option here"

Project->Properties->Java Compiler->Errors/Warnings

Enable project specific settings

Answer 4

One way to do this is to add @SuppressWarning(...) annotations to the source code.

Another way would be to move the troublesome code to a separate Eclipse project and use per-project compiler settings.

EDIT

Surely, you can partition your code into multiple projects with the appropriate inter-project dependencies?

If not, I'd say you are out of realistic options. (But if you want some unrealistic ones, you could post-process the generated code to add the annotations, hack the Eclipse Java compiler to implement per-file suppression, hack the Eclipse "Problems" view to implement per-file/directory filtering of errors, etc, etc.)

Answer 5

If you want to hide warnings on a class or on a method, see the Eclipse documentation on the @SuppressWarnings annotation or Java documentation

Example:

@SuppressWarnings("unused")
public void foo() {
    String s;
}