Does the bundle export those packages in both versions? 2.0 and 2.1 or just 2.1. In that case I'd make sure those packages which are valid for 2.0 and 2.1 are exported for both and only the new ones exported as 2.1. It's the same "workaround" that I've needed to do for Pax Web Jetty bundle to export both a 2.6 Servlet API and 3.0
regards, Achim 2014-09-16 13:09 GMT+02:00 Jean-Baptiste Onofré <[email protected]>: > By the way, it's weird that JPA 2.1 is not backward compatible with JPA > 2.0: the interfaces contains the same methods (plus some addition). > > Do you have an use case to test ? > > 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 > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Software Architect / Project Manager / Scrum Master
