We've been overriding various features to tailor the dependencies in our setup. Not ideal nor easy to maintain. An exclude would be great for us as well.
-Nick Sent from my BlackBerry. I am AFK at the moment Original Message From: Jean-Baptiste Onofré Sent: Sunday, December 7, 2014 12:28 PM To: [email protected] Reply To: [email protected] Subject: Re: Dependency on Camel brings in a jaxb impl that causes a use constraint violation Hi, The karaf-maven-plugin resolves recursively all features/bundles. However, you raise a valid point: I will create a Jira to add <excludes/> for features and bundles, to give more control. Thanks, Regards JB On 12/07/2014 12:08 PM, MarkD wrote: > Hi all, > > I have a dependency on Camel which is added to the feature list in my kar by > the karaf maven plugin. > > It has a transitive dependency on jaxb-impl which I think is exposed by the > system bundle. Is there any way of telling the karaf maven plugin to ignore > this so I only get the provided bundle? > > Thanks in advance! > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Dependency-on-Camel-brings-in-a-jaxb-impl-that-causes-a-use-constraint-violation-tp4037029.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
