Hi Roland

The standard proposal in this context is to not deploy the org.osgi.compendium 
bundle.

While it sounds nice in the first place to have a single bundle with all the 
OSGi APIs, in practice it generates more pains than solutions ..

The reason for this is that the compendium bundle rarely exposes the actual API 
versions expected by the API implementations. For this reason we in Apache 
Felix project provide the service API as part of the actual service 
implementation. This makes for much stabler deployments.

Regards
Felix


Am 20.06.2013 um 16:01 schrieb Roland:

> Hi everyone,
> 
> today I ran into the issue "loader constraint violation". I figured out that
> this is caused by gogo-command which exports the package
> org.osgi.service.log that is also exported by org.osgi.compendium. How can I
> prevent my own bundle to import org.osgi.service.log from
> org.apache.felix.gogo.command? Why gogo-command exports this package?
> 
> by the way...
> I also have a problem with gogo-command in my auto-generated OBR-file (by
> maven-obr-plugin).
> This line throws an java.lang.Exception:
> <require extend="false"
> filter="(&amp;(package=org.apache.felix.service.command)(version&gt;=0.10.0)(version&lt;1.0.0)(status=provisional)(mandatory:&lt;*status))"
> multiple="false" name="package" optional="false">Import package
> org.apache.felix.service.command ;version=[0.10.0,1.0.0)</require>
> I don't no why...
> 
> Many thanks in advance!
> Roalnd
> 
> 
> 
> 
> --
> View this message in context: 
> http://apache-felix.18485.x6.nabble.com/Loader-constraint-violation-gogo-command-exports-org-osgi-service-log-tp5004055.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to