I don't think you will find such a thing, but if you do, let us know
What we do is exclude particular dependencies, since most of them are osgi
and are to be included; but this probably isn't your case. Some of our osgi
dependencies have an "osgi" classifier but not all so we can't use that to
dec
Hello,
The org.apache.maven.plugins.shade.resource.AppendingTransformer in the
maven shade plugin (v 2.0) only supports exact resource name matches for
appending resources for the uber jar. Do you guys see any problems if this
this supports patterns that might be able to do it for a bunch of resou
Hi,
I am creating a Maven assembly that copies required dependencies to a "lib"
directory. Since it is an OSGi based application, I would like to exclude
non-OSGi based (transitive) dependencies automatically when my module's
assembly is processed.
>From maven dependency plugin and assembly descr
I'm not sure I got everything that you've said, but that looks right.
Vincent
2013/7/4 Mirko Friedenhagen :
> Hello Vincent,
>
> thanks for your answer. Just so I get this right: I am looking at my
> IT-pom [1] and it has no parent defined. I am running Apache Maven
> 3.0.5. In my output I *do n
Hello,
The org.apache.maven.plugins.shade.resource.AppendingTransformer in the
maven shade plugin (v 2.0) only supports exact resource name matches for
appending resources for the uber jar. Do you guys see any problems if this
this supports patterns that might be able to do it for a bunch of resou
Hello Vincent,
thanks for your answer. Just so I get this right: I am looking at my
IT-pom [1] and it has no parent defined. I am running Apache Maven
3.0.5. In my output I *do not* see the plugin-versions defined in the
super POM from Maven-core (this are the ones defined in
default-bindings.xml
