Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

I agree about the messy part with blacklisting. It's a good way to keep from being blocked from an issue you otherwise can't around, is how I look at it. I guess I hope that eventually there will be an awareness by developers around putting a little more thought into code organization and

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

> Jean-Baptiste Onofré : > you can blacklist or you can exclude artifacts. Right. I tried using blacklisting in the karaf-maven-plugin documentation, but that didn't work as I expected it to. I looked for something like the exclusion of artifacts in the karaf-maven-plugin documentation,

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

> Ryan Moquin : > Hi Steinar, > There are a couple ways. > 1. You can use runtime to prevent a jar from being added, > but that has other ramifications when building (such as I think unit test > code won't see the dependency) > 2. You can use provided to only include that dependency but >

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

Hi, you can blacklist or you can exclude artifacts. You can also use a different scope than compile, or use a features.xml "template". Regards JB On 31/08/2019 00:52, Steinar Bang wrote: > Is it possible to make karaf-maven-plugin exclude some dependencies with > compile? > > I'm trying to

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

Hi Steinar, There are a couple ways. 1. You can use runtime to prevent a jar from being added, but that has other ramifications when building (such as I think unit test code won't see the dependency) 2. You can use provided to only include that dependency but not of it's transitive dependencies