|
||||||||
|
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 |
||||||||
Can someone at least acknowledge that they have SEEN this issue? I can understand if there is some roadblock to the issue being fixed, or if there are just higher-priority fixes to be considered, but I have seen bug after bug after bug responded to within hours or days of posting, and this issue doesn't have so much as a "thanks for the report, we'll look into it" comment after three months.
This is a BLOCKING bug. I cannot test anything related to the JPA 2.1 converter features at all, which means there could be unknown numbers of minor converter bugs not being detected leading up to the release of 4.3.