Why shouldn't gogo-command export org.osgi.service.log? Also if your bundle imports the package, it shouldn't care which particular bundle it comes from. This is a fundamental principle of OSGi.
Unfortunately you didn't give any details of the constraint violation error, so it's anybody's guess why it happened or what the proper fix should be. On Thu, Jun 20, 2013 at 3:01 PM, Roland <[email protected]> wrote: > 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="(&(package=org.apache.felix.service.command)(version>=0.10.0)(version<1.0.0)(status=provisional)(mandatory:<*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]
