|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Well here is the problem. Monday 4.2 will go Final. There are changes associated with this issue that will get released with that. At which point this issue will get closed. So either:
I am busy with the JPA 2.1 TCK so I will absolutely not have time to look into this. Maybe someone else from the Hibernate team does. But, Marc, if you want to make sure this gets into that 4.2 Final, my suggestion is to look into it yourself; you can follow along the changes already made to see the code paths changed to fix the problems demonstrated in my test.
I'll re-open this one for now, but expect on Monday it to get moved back to resolved and then closed one way or another...
<soapbox>
IMO this illustrates all the more the importance of attaching test cases with bug reports. I initially asked for that many months ago and got no response. I had to create my own tests reproducing the issue. Those tests I created obviously did not cover (all) the actual code paths involved in this. Had a workable test case been included up front this likely might have been resolved already completely.
And yes I understand Marc that you did upload a test case, but that was just a week ago; a week before the discussed release.
</soapbox>