[
http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-33?page...
]
Hardy Ferentschik commented on METAGEN-33:
------------------------------------------
It seems Eclipse is depending on an optional feature. AFAIU @Generated is optional. The
problem with adding it to the static metamodel is that @Generated was added only in Java
6. This means a meta model containing @Generated will not work in a Java 5 JVM which seems
to be an unnecessary restriction.
We could introduce a flag to the processor which when enabled adds @Generated to the
metamodel classes. This way it is up to the user to decide whether the code should be able
to run in a Java 5 JVM.
Metamodel is not generated with @Generated annotation
-----------------------------------------------------
Key: METAGEN-33
URL:
http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-33
Project: Hibernate Metamodel Generator
Issue Type: Task
Components: processor
Affects Versions: 1.0.0.Final
Environment: hibernate 3.5.4 and final metamodel version
Reporter: Paulo Silveira
Assignee: Hardy Ferentschik
The static meta model does not have a @Generated. This is probably the reason that avoids
Eclipse compiling of the derived classes (we must clean the project, or alter the
generated class and save it). The eclipselink metamodel generator works fine, and the only
difference between EclipseLink generator and hibernate generator is this annotation
You can see that many users are being affected by this issue in the comments here:
http://relation.to/Bloggers/HibernateStaticMetamodelGeneratorAnnotationPr...
--
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