You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2014/04/25 08:28:14 UTC
[jira] [Resolved] (CAMEL-7377) mark openjpa as dependency in Camel
JPA feature
[ https://issues.apache.org/jira/browse/CAMEL-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-7377.
--------------------------------
Resolution: Fixed
> mark openjpa as dependency in Camel JPA feature
> ------------------------------------------------
>
> Key: CAMEL-7377
> URL: https://issues.apache.org/jira/browse/CAMEL-7377
> Project: Camel
> Issue Type: Bug
> Components: camel-jpa, karaf
> Affects Versions: 2.12.3, 2.13.0
> Reporter: Ioan Eugen Stan
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.12.4, 2.13.1, 2.14.0
>
>
> I believe Camel-JPA feature should mark openjpa bundle as a dependency becasue it conflicts with open-jpa 2.3.0.
> Currently camel-jpa feature.xml defines:
> ```
> <bundle>mvn:org.apache.openjpa/openjpa/2.2.2</bundle>
> ```
> and should be <bundle dependency="true">mvn:org.apache.openjpa/openjpa/2.2.2</bundle>
> This problem apears when you have openjpa 2.3.0 installed and with to install camel-jpa 2.12.3 feature.
> Not marking the bundle as a dependency results in camel-jpa pulling the OpenJPA 2.2.2 bundle even if karaf has OpenJpa 2.3.0. Since both bundles try to register a PersistenceProvider in OSgi, the second one fails and the bundle fails to start - so camel-jpa feature is not installed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)