Hello,
Some time ago I've started a thread about building Karaf distribution with
maven plugin, and with your help, I've got a working example.
However, now it's time to add another version of some feature to the
distribution (groupId and artifactId are the same, only the version differ,
this is exactly why I need OSGi container instead of, say, Jetty).
I have the dependencies in my pom.xml:
<dependency>
<groupId>com.example</groupId>
<artifactId>some-features</artifactId>
<version>2.5.0-SNAPSHOT</version>
<classifier>features</classifier>
<type>xml</type>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>com.example</groupId>
<artifactId>some-features</artifactId>
<version>3.0.0-SNAPSHOT</version>
<classifier>features</classifier>
<type>xml</type>
<scope>runtime</scope>
</dependency>
And boot features definition:
<bootFeatures>
...
<feature>my-feature-2</feature>
<feature>my-feature-3</feature>
</bootFeatures>
However, I see, that only the newest version (3) is installed. I see no error
in logs.
The whole setup works perfectly in stand-alone karaf, where the
org.apache.karaf.features.cfg is manually edited. But when building using karaf
plugin, it looks like the other feature is totally ignored.
It has likely to do with inability of Maven to deal with more than 1 version of
one dependency in single project? If so, how to work around it? Is there any
other way to 'tell' karaf plugin about required dependencies than pom.xml?
Best regards,
Lukasz Lech
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
