You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Clement Escoffier (JIRA)" <ji...@apache.org> on 2014/12/02 16:39:13 UTC

[jira] [Commented] (FELIX-4716) Bundle org.apache.felix.ipojo physically contains OSGi API classes

    [ https://issues.apache.org/jira/browse/FELIX-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231646#comment-14231646 ] 

Clement Escoffier commented on FELIX-4716:
------------------------------------------

iPOJO embeds theses classes to be standalone. We should update the embedded version to avoid the issue (and to always use the latest API).

> Bundle org.apache.felix.ipojo physically contains OSGi API classes
> ------------------------------------------------------------------
>
>                 Key: FELIX-4716
>                 URL: https://issues.apache.org/jira/browse/FELIX-4716
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: ipojo-runtime-1.12.0
>         Environment: ubuntu 14, karaf
>            Reporter: Karl Leopold
>
> The _org.apache.felix.ipojo_ bundle imports, exports and physically contains interface-classes of packages _org.osgi.services.cm_ and _org.osgi.services.log_, both with version 1.3.
> I'm running ipojo in karaf 3.0.2. There, these osgi-packages also exists, just in another version.
> Sometimes it happens that a bundle of mine, which has a package-dependency on _org.osgi.services.cm_ is bound to the ipojo-version instead of the one of felix/karaf. Now, the bundle is resolved, but the service dependency on the ConfigurationAdmin can never be resolved, because the implementation is incompatible to the imported interface.
> I can fix that, if I play around with the bundle start levels.
> Anyway, I think it's a bug in iPOJO, because it should not inline any OSGi API packages.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)