[
http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-50?page...
]
Hardy Ferentschik commented on METAGEN-50:
------------------------------------------
I thought I already commented once before on this, but maybe not ;-)
{quote}
1) Entities marked as @Deprecated.
{quote}
How can a @Deprecated annotation create a problem/warning which needs suppressing in the
metamodel?
{quote}
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.
{quote}
Can you provide a testcase/example?
Suppress Warnings
-----------------
Key: METAGEN-50
URL:
http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-50
Project: Hibernate Metamodel Generator
Issue Type: Improvement
Components: processor
Affects Versions: 1.1.1.Final
Reporter: Stephan Bublava
Assignee: Hardy Ferentschik
Priority: Minor
Please consider adding a @SuppressWarnings("all") annotation to the generated
classes. Warnings in generated code are not helpful.
In my case the warnings (driven by IDE settings) are caused by:
1) Entities marked as @Deprecated.
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira