Well, if they show up in red, that means they're unsatisfied. Check the headers for the dependencies as well to make sure they're exporting everything properly. Sometimes you need to install artifacts with wrap: before the mvn: to add OSGi metadata.
On 16 June 2014 23:10, SapnaB <[email protected]> wrote: > Hi Matt, > > I get manifest headers as well as the import/export packages with > dependencies, when I run osgi:headers on the above Bundle ids. The command > run on my bundle gives: > > Apache Karaf :: Shell test/test-mcds Commands (370) > ------------------------------------------------------- > Manifest-Version = 1.0 > Bnd-LastModified = 1402976384349 > Tool = Bnd-1.50.0 > Built-By = sapbharg > Build-Jdk = 1.6.0_24 > Created-By = Apache Maven Bundle Plugin > > Bundle-Name = Apache Karaf :: Shell test/test-mcds Commands > Bundle-Description = Provides the test custom command > Bundle-SymbolicName = Test > Bundle-Version = 0.0.1.SNAPSHOT > Bundle-ManifestVersion = 2 > > Import-Package = > com.sun.jersey.api.client;version="[1.18,2)", > com.sun.jersey.api.client.config;version="[1.18,2)", > javax.ws.rs.core;version="[1.1,2)", > org.apache.felix.gogo.commands;version="[0.10,1)", > > org.apache.felix.service.command;status=provisional;version="[0.10,1)", > org.apache.karaf.shell.console;version="[2.2,3)", > org.osgi.service.blueprint;version="[1.0.0,2.0.0)" > Export-Package = > test.command; > uses:="org.apache.karaf.shell.console, > com.sun.jersey.api.client.config, > org.apache.felix.gogo.commands, > com.sun.jersey.api.client, > javax.ws.rs.core"; > version=0.0.1.SNAPSHOT > > Is there anything specific ur looking at? > > -Sapna > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Missing-Constraint-Import-Package-com-sun-jersey-api-client-tp4033550p4033556.html > Sent from the Karaf - Dev mailing list archive at Nabble.com. > -- Matt Sicker <[email protected]>
