Page History

...

The plugin uses the <Embed-Dependency> instruction to transform the project dependencies into <Include-Resource> and <Bundle-ClassPath> clauses, which are then appended to the current set of instructions and passed onto BND. If you want the embedded dependencies to be at the start or middle of <Include-Resource> or <Bundle-ClassPath> then you can use {maven-dependencies}, which will automatically expand to the relevant clauses.

some examples:

<Embed-Dependency>*;scope=compile|runtime</Embed-Dependency>

<Embed-Dependency>junit;scope=test</Embed-Dependency>

<Embed-Dependency>aopalliance;scope=!test;inline=true</Embed-Dependency>

<Include-Resource>{maven-resources},{maven-dependencies},org/foo/Example.class=target/classes/org/foo/Example.class</Include-Resource>

<Bundle-ClassPath>.,{maven-dependencies},some.jar</Bundle-ClassPath>

By default matched dependencies are embedded in the bundle as artifactId-version.jar. This behaviour can be modified using the following instructions:

...