Thanks for bringing
attention. That was just carelessness on my part. I have resolved it
indicative of a larger, though pretty isolated, issue. It only affects
users wanting to use what JPA terms a "static metamodel". The
referenced error is happening when trying to "wire up" the static
metamodel classes. The underlying issue is various mismatches between
how JPA defines the metamodel and how Hibernate defines it. The
long-term fix for this is substantial. I nudged the issue author for
some more details. I agree it would be nice to have all these static
metamodel issues resolved prior 3.5.0, but given that users don't really
know about this feature thus far (the actual generator has no
documentation/fanfare and the spec does not really dwell on the
specifics) I don't see that as necessarily feasible at this time.
On 02/17/2010 01:40 AM, Guenther Demetz wrote:
I know 2 unassigned bug issues which only 3.5 is affect and not former
I think this issues should be fixed for backward compatibility reasons.
Overmore there are further unassigned 47 bug issues on jira with version
3.5 set as affectedVersion (see JQL query below).
I haven't the time to analyze them one by one, but I fear there are some
other bug's which are affect to 3.5 only
and thus may compromise 3.5's backward compatibility.
JQL Query: resolution = Unresolved AND affectedVersion >= "3.5.0.Beta-1"
AND affectedVersion not in
AND fixVersion = EMPTY and assignee = null AND type = "bug" ORDER BY key
Steve Ebersole schrieb:
> Just wanted to point out to everyone that 3.5.0-CR-2 has been set up in
> JIRA (
> ) and tentatively scheduled for Feb 24 2010. I say tentatively because
> I am not sure I will wait that long; lets see how things go.
> In the meantime, I moved all unresolved issues not in progress to 3.5.x.
> Please take the time asap to mark any issues you want in 3.5.0-CR-2.
> I completely expect this to be the last CR before 3.5.0