felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4716) Bundle org.apache.felix.ipojo physically contains OSGi API classes
Date Wed, 03 Dec 2014 10:50:12 GMT

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

Christian Schneider commented on FELIX-4716:

Embedding packages from the OSGi compendium or enterprise APIs is quite common practice. If
importers of the packages specify correct import ranges this normally should not pose a problem.

> 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
>            Assignee: Clement Escoffier
> 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
> 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

View raw message