Should I compose a class of constants for my annotations?

Question

What's better?

• @SuppressWarnings("unchecked")
• @SuppressWarnings(AnnotationConstants.UNCHECKED)

Where AnnotationConstantsis a typical class of constants ...

public final class AnnotationConstants {
    private AnnotationConstants() { }

    public static final String UNCHECKED = "unchecked";

    ...
}

I know that there are many common arguments for classes of constants and against them - and that’s exactly what I'm not interested in . I want to know if the class of constants is really for annotations, a good idea or a bad idea.

Answer 1

In this particular example, I would stick with literals. In the end, you are trying to suppress warnings - if you use the wrong literal, the warning will not be suppressed, which will draw your attention to the problem.

Answer 2

, .

Spring - @Scope (Scopes.SESSION) @Scope (Scopes.REQUEST), , , , .

, , , .

Answer 3

Holsam SuppressWarnings -

, usng, , ,

Answer 4

@SuppressWarning , . , , . Eclipse .