> Is it the case for a big bundle too ?
Well the big bundle pulls in a bunch of other org.apache.cxf.tools.wsdlto* packages, not just org.apache.cxf.tools.wsdlto.core. But obviously that's the right thing to do in the big bundle case, as all classes form the cxf-tools-wsdlto-* modules are actually included in the big bundle. Whereas in the minimal bundle, *only* the org.apache.cxf.tools.wsdlto.core package is imported/exported. This causes a runtime failure as the package cannot be resolved due to the cxf-tools-wsdlto-* classes being excluded. /Eoghan -----Original Message----- From: Sergey Beryozkin [mailto:[EMAIL PROTECTED] Sent: Wed 11/26/2008 9:12 AM To: [email protected] Subject: Re: Problem with cxf-bundle-minimal Hi Eoghan In this case it looks like some other module recursively pulls in cxf-tools-wsdlto-* ... Is it the case for a big bundle too ? Cheers, Sergey ----- Original Message ----- From: "Eoghan Glynn" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, November 26, 2008 1:58 PM Subject: Problem with cxf-bundle-minimal Folks, For some reason the minimal bundle lists org.apache.cxf.tools.wsdlto.core in its Import- & Export-Package manifest headers, even though the cxf-tools-wsdlto-* modules are excluded from this bundle. The net result is an unresolved package error when the minimal bundle is installed. Anyone know why this unnecessary dependency is pulled into the bundle manifest? Cheers, Eoghan
