I'm afraid that I must have missed the initial discussion for doing a new release of Aries JPA, so this is a now a bit late.
While working on my demo for the OSGi community event I discovered a small bug in the Aries JPA container (https://issues.apache.org/jira/browse/ARIES-1631) I assume that it's now too late to get this fixed? Regards, Tim On 28 Oct 2016, at 14:15, Grzegorz Grzybek <[email protected]<mailto:[email protected]>> wrote: +1 (non-binding) regards Grzegorz 2016-10-28 13:48 GMT+02:00 Daniel Kulp <[email protected]<mailto:[email protected]>>: +1 Dan On Oct 28, 2016, at 5:23 AM, Christian Schneider < [email protected]<mailto:[email protected]>> wrote: I've staged a release for vote at: https://repository.apache.org/content/repositories/orgapachearies-1089 Release Notes - Aries jpa-2.5.0 ** Bug * [ARIES-1494] - Exception when calling a transactional method twice from a non transaction method * [ARIES-1575] - Aries JPA should use the persistence bundle's context to obtain the Persistence Provider service * [ARIES-1615] - Calling the method createAndCloseDummyEMF() causes NullPointerException ** Improvement * [ARIES-1629] - Remove persistence-api feature from aries jpa feature repo https://issues.apache.org/jira/browse/ARIES/fixforversion/12335940 Please review and vote: [ ] +1 Release the above artifacts [ ] -1 Do not Here is my +1 Cheers, Christian -- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com -- Daniel Kulp [email protected]<mailto:[email protected]> - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
