Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 1 Apr 2011 19:05:06 +0000 (UTC)
From: "Jonathan Anstey (JIRA)" <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <366416661.29296.1301684706049.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CAMEL-3829) geronimo-jpa_3.0_spec dependency on
 camel-jpa has bad OSGi package export
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

geronimo-jpa_3.0_spec dependency on camel-jpa has bad OSGi package export
-------------------------------------------------------------------------

                 Key: CAMEL-3829
                 URL: https://issues.apache.org/jira/browse/CAMEL-3829
             Project: Camel
          Issue Type: Improvement
    Affects Versions: 2.7.0
            Reporter: Jonathan Anstey
            Assignee: Jonathan Anstey


The geronimo-jpa_3.0_spec artifact actually imports/exports the JPA API as version *3*

Import-Package: javax.persistence;version="3.0"
Export-Package: javax.persistence;uses:="javax.persistence.spi";version="3.0"

When this is actually version 1 of the JPA spec of course, not version 3. This is fine in OSGi currently because we override this import in camel-jpa with

Import-Package: javax.persistence;version="[1.1,2)"

However, if someone depends on camel-jpa in their own Maven pom, the maven-bundle-plugin sets the import as 

Import-Package: javax.persistence;version="3.0"

which is incorrect. I'm going to switch this dependency to the fixed JPA bundle published in ServiceMix specs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira