[jira] [Updated] (OPENJPA-2240) JVMVRFY012 when using openjpa together with hyperjaxb3

[ https://issues.apache.org/jira/browse/OPENJPA-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Albert Lee updated OPENJPA-2240: Fix Version/s: 2.2.2 > JVMVRFY012 when using openjpa together with hyperjaxb3 > -

[jira] [Resolved] (OPENJPA-2320) CriteriaBuilder predicate construction deadlocks in multi-core VM due to static initializer

[ https://issues.apache.org/jira/browse/OPENJPA-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2320. Resolution: Fixed > CriteriaBuilder predicate construction deadlocks in multi-core VM

[jira] [Resolved] (OPENJPA-2321) Synchronizing logging output stream causes deadlock when used some JDK LogManger derivative

[ https://issues.apache.org/jira/browse/OPENJPA-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2321. Resolution: Fixed > Synchronizing logging output stream causes deadlock when used som

[jira] [Resolved] (OPENJPA-2304) Thread deadlock in CriteriaBuilder

[ https://issues.apache.org/jira/browse/OPENJPA-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar resolved OPENJPA-2304. Resolution: Fixed > Thread deadlock in CriteriaBuilder >

[jira] [Created] (OPENJPA-2321) Synchronizing logging output stream causes deadlock when used some JDK LogManger derivative

Pinaki Poddar created OPENJPA-2321: -- Summary: Synchronizing logging output stream causes deadlock when used some JDK LogManger derivative Key: OPENJPA-2321 URL: https://issues.apache.org/jira/browse/OPENJPA-2321

Re: metamodel with maven compiler 3.0?

openjpa needs fork to true (to pass the param) but when forking dependencies are not propagated, i'll get in touch with maven@ thanks for the pointers *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/*

Re: metamodel with maven compiler 3.0?

Hi Romain, I agree that it should have been compatible. When I look at the documentation for the setting [1], it looks like also needs to be set to "true". But, I can't tell where this processing changed between 2.x and 3.x of the plugin. The OpenJPA build scripts don't seem to use this partic

Re: metamodel with maven compiler 3.0?

Hi Kevin, i would have expected it to be compatible and was looking for some input why this compatibility was broken updating maven compiler plugin ( http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11130&version=18537 doesn't show anything which could imply it) *Romain Manni-Bucau* *Tw

Re: metamodel with maven compiler 3.0?

Hi Romain, Is there some reason why you must use Maven 3.0? Since OpenJPA identified it's requirement as 2.5.1, I'm not clear on what the question or issue is. If you want to figure out how OpenJPA can support Maven 3.0, then submitting a proposed patch would be beneficial and welcome. Thanks, Ke