[
https://issues.apache.org/jira/browse/CAMEL-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Anstey resolved CAMEL-3829.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
janstey@duffman:/x1/asf/camel/trunk$ svn ci parent/pom.xml
components/camel-jpa/pom.xml -m "CAMEL-3829 - geronimo-jpa_3.0_spec dependency
on camel-jpa has bad OSGi package import/export"
Sending components/camel-jpa/pom.xml
Sending parent/pom.xml
Transmitting file data ..
Committed revision 1087856.
> 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
> Fix For: 2.8.0
>
>
> 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
