Not sure what you mean by filter on the use clause. The use clause are on exported package and refer to imported packages, and afaik, there's no way to filter those. A good way to force a wiring is to add an import package to the one that is used, that way, the osgi resolver does not have any choice (for class space consistency reason).
On Wed, Jun 20, 2012 at 11:40 PM, Romain Gilles <[email protected]> wrote: > Hi Guillaume, > Is it possible to force the wiring to gemini-blueprint by a filter on the > 'use' close? > > Romain. > > 2012/6/20 Romain Gilles <[email protected]> >> >> Thank you >> ;) >> >> 2012/6/20 Romain Gilles <[email protected]> >>> >>> This is a good tip to know thank you. >>> I m >>> >>> Romain. >>> >>> 2012/6/20 maaruks <[email protected]> >>>> >>>> I restarted karaf and blueprint starts now. >>>> >>>> -- >>>> View this message in context: >>>> http://karaf.922171.n3.nabble.com/Bundle-is-not-compatible-with-this-blueprint-extender-tp4024898p4024910.html >>>> Sent from the Karaf - User mailing list archive at Nabble.com. >>> >>> >> > -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ FuseSource, Integration everywhere http://fusesource.com
