[
https://issues.apache.org/jira/browse/FELIX-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231678#comment-14231678
]
Karl Leopold commented on FELIX-4716:
-------------------------------------
Oh no, please don't do that...
Now, I can work around this issue by tuning start-levels, so that they're
started the newer config-admin API is running. Since it is newer, it is
preferred over the API exported by iPOJO. If both bundles export
org.osgi.services.* with the same version, I have to look for another hack to
get my stuff running correctly.
And I still think, that it's not a good idea to inline AND export these
packages. If iPOJO has a dependency on the OSGi-compendium, then it should be.
And having the OSGi-compendium API in an OSGi container is not that uncommon :)
.
What about making the dependency on org.osgi.services.* optional? Then, I'll
have a lot of trouble at runtime with checking whether it's there or not, but
in the end it should be possible.
> 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)
