Here is a patch for the 1.2.0-SNAPSHOT version of the Hibernate JPA 2 Metamodel Generator that provides an option to add the @SuppressWarnings("all") annotation to generated classes. The usage is the same than for the @Generated annotation. You have to set -AaddSuppressWarningsAnnotation=true.

Hope this helps,

–

Théo Chamley

I guess we could make it a configuration option of the processor.

How can a @Deprecated annotation create a problem/warning which needs suppressing in the metamodel?

We have set "Deprecated API" to "Warning" in Eclipse (Preferences -> Java -> Compiler -> Errors / Warnings), which triggers Eclipse warnings for all references to deprectated constructs.

If Foo.java is deprecated then Eclipse will warn about all attribute definitions in Foo_.java

Can you provide a testcase/example?

Here's a simplified example:

The custom type uses the binary representation of the column value for mapping; for example: 5 => 2^0 + 2^2 => {0, 2} => {RED, BLUE}. I've omitted the actual implementation, because it doesn't influence the meta-model, which looks like this:

Since it contains EnumSet instead of EnumSet<Color>, there are Eclipse warnings as well (with the settings we are using).

I thought I already commented once before on this, but maybe not

1) Entities marked as @Deprecated.

How can a @Deprecated annotation create a problem/warning which needs suppressing in the metamodel?

2) A custom Hibernate user type that maps a numeric SQL type into an EnumSet<T>. The generated SingularAttribute does not preserve the type of the set.

Can you provide a testcase/example?