Hi Christian,
I agree, and I would propose to align version with JPA versions.
Let say:
1/ Aries jpa 1.0.x is JPA 2.0
2/ Aries jpa 1.1.x is JPA 2.1
and use corresponding branches.
Like this, in Karaf, the features will align the Aries JPA version with
the JPA level expected by the persistence engine.
Guillaume committed a change to have a jpa and jpa20 modules.
It's an alternative, but it means lot of code duplication.
If you are agree, I will do this change.
@Guillaume, @Christian, ok for you ?
Regards
JB
On 09/16/2014 10:57 AM, Christian Schneider wrote:
Hi all,
we have the issue https://issues.apache.org/jira/browse/ARIES-1234 in
aries jpa container.
The current release of jpa container fixes some quite critical bugs but
is now incompatible to aries jpa 2.0.
I propose we revert back to the code before the jpa 2.1 upgrade, then do
a new release that just contains the fixes.
We can then work on some support for jpa 2.1 that is compatible or
advise people to use different jpa container versions depending if they
want jpa 2.1 or 2.0 support.
wdyt?
Christian
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
