IIRC, all the dependencies in the pom are included in the component installer provided that: * the scope is runtime * the dependency is not included in a JBI dependency (i.e. a shared library) Maybe if you run maven with -X, you will find some useful informations...
On 2/13/07, Terry <[EMAIL PROTECTED]> wrote:
I'm not sure I have got my head around all the dependency issues. I have a JBI Binding Component that depends upon a java library. When I unit test the component embedded all works correctly, however if I then attempt to deploy a service unit that uses the binding component, it fails to start with a NoClassDefFoundError on one of the classes in the java library. If I look at the packaging for the BC, I see no sign of the java library included with the BC for deployment although it exists as a dependency within the POM for the BC and works in the unit tests. Do I need to implement something to cause the java library to be included in the jar for the BC? Terry gnodet wrote: > > Yeah. Unfortuanately the JBI spec does not support any reference > to a shared library from a service unit, but this is a really needed > feature > and will hopefully be implemented in 3.2. > > -- View this message in context: http://www.nabble.com/Sharing-servicemix-SE-BC-dependencies-tf3205678s12049.html#a8940848 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
