Return-Path: X-Original-To: apmail-karaf-issues-archive@minotaur.apache.org Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4DAA810BBE for ; Sat, 27 Dec 2014 11:01:13 +0000 (UTC) Received: (qmail 44890 invoked by uid 500); 27 Dec 2014 11:01:13 -0000 Delivered-To: apmail-karaf-issues-archive@karaf.apache.org Received: (qmail 44862 invoked by uid 500); 27 Dec 2014 11:01:13 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 44851 invoked by uid 99); 27 Dec 2014 11:01:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Dec 2014 11:01:13 +0000 Date: Sat, 27 Dec 2014 11:01:13 +0000 (UTC) From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KARAF-3393) Provide ready to use jpa20 and jpa21 features MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KARAF-3393?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1425= 9337#comment-14259337 ]=20 Jean-Baptiste Onofr=C3=A9 commented on KARAF-3393: --------------------------------------------- Instead of introducing jpa-api features, I just duplicate the jpa one with = different version/api. > Provide ready to use jpa20 and jpa21 features > --------------------------------------------- > > Key: KARAF-3393 > URL: https://issues.apache.org/jira/browse/KARAF-3393 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature > Reporter: Jean-Baptiste Onofr=C3=A9 > Assignee: Jean-Baptiste Onofr=C3=A9 > Fix For: 4.0.0, 3.0.3, 2.4.1 > > > As discussed with Christian on the mailing list, to avoid JPA API mismatc= h and easily support both JPA 2.0 and JPA 2.1, we should provide ready to u= se jpa features, matching the jpa spec level that the user needs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)