I have the following in dependencies for a maven bundle project that
uses karaf-maven-plugin to generate a feature repository:
<dependencies>
<dependency>
<groupId>no.priv.bang.karaf</groupId>
<artifactId>karaf.liquibase.sample.services</artifactId>
<version>${project.version}</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>no.priv.bang.karaf</groupId>
<artifactId>karaf.liquibase.sample.services</artifactId>
<version>${project.version}</version>
<classifier>features</classifier>
<type>xml</type>
</dependency>
<dependency>
<groupId>no.priv.bang.karaf</groupId>
<artifactId>karaf.liquibase.sample</artifactId>
<version>${project.version}</version>
<classifier>features</classifier>
<type>xml</type>
</dependency>
Only the karaf.liquibase.sample feature dependency is added to the generated
feature repository:
https://gist.github.com/steinarb/e975457a818c593477e96c4dd34bbeba
Is this because I have both a jar file dependency and a feature/xml
dependency to the same project?
If so, is this intended behaviour? Or is this a bug?
Or is the problem somewhere else? Somewhere in my maven config?
I haven't pushed this change, but the project is here:
https://github.com/steinarb/liquibase-karaf-feature/blob/master/liquibase-integration-test/karaf.liquibase.sample.datasource.receiver/pom.xml#L23
It's a bundle project that's created as an integration test for my
liquibase karaf feature.
Thanks!
- Steinar