I have an OSGi project that includes the sesame-runtime-osgi dependency with a compile scope.

```
<dependency>
    <groupId>org.openrdf.sesame</groupId>
    <artifactId>sesame-runtime-osgi</artifactId>
    <version>${sesame.version}</version>
    <exclusions>
        <exclusion>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
        </exclusion>
    </exclusions>
</dependency>

```

The sesame-runtime-osgi artifact includes several runtime dependencies. For example:

```
+- org.openrdf.sesame:sesame-runtime-osgi:jar:2.7.13:compile
|  +- org.openrdf.sesame:sesame-http-client:jar:2.7.13:compile
|  |  +- org.openrdf.sesame:sesame-http-protocol:jar:2.7.13:compile
|  |  |  \- org.openrdf.sesame:sesame-rio-ntriples:jar:2.7.6:compile
|  |  |     \- commons-io:commons-io:jar:2.1:compile
|  |  +- org.openrdf.sesame:sesame-query:jar:2.7.13:compile
.
.
.
|  |  \- commons-codec:commons-codec:jar:1.4:runtime
|  \- org.openrdf.sesame:sesame-http-server-spring:jar:2.7.13:compile
|     +- org.openrdf.sesame:sesame-runtime:jar:2.7.6:compile
|     |  +- org.openrdf.sesame:sesame-repository-manager:jar:2.7.13:compile
.
.
.
|     |  +- org.openrdf.sesame:sesame-queryresultio-sparqljson:jar:2.7.13:runtime
|     |  |  \- com.fasterxml.jackson.core:jackson-core:jar:2.2.2:runtime
|     |  +- org.openrdf.sesame:sesame-queryresultio-text:jar:2.7.13:runtime
|     |  |  \- net.sf.opencsv:opencsv:jar:2.0:runtime
.
.
.
|     \- cglib:cglib:jar:2.2:compile
|        \- asm:asm:jar:3.1:compile

```

You'll notice that "net.sf.opencsv:opencsv:jar:2.0" is a runtime dependency so it is not included in the feature.xml generated by the karaf-maven-plugin. Unfortunately the package needed at runtime **is** included in the "Import-Packages" directive in the sesame-runtime-osgi Manifest:

```
Import-Package: au.com.bytecode.opencsv

```

so Karaf cannot deploy the feature unless I manually wrap and deploy the runtime dependencies myself. Obviously I don't want to have to do that.

Is there a way I can include dependencies with runtime scope in the feature.xml generation?

Thanks