I think pax-exam has its own features parser, so it may have been kept
behing what karaf provides.
We really need to use a schema and version that to be able to detect
such problems more easily.
On Fri, Nov 5, 2010 at 10:17, Andreas Gies <andr...@wayofquality.de> wrote:
> Hello,
>
> I am sorry if am hitting the wrong list with my question, but it seemed a
> good starting point for me ...
>
> We have started the development of a karaf based application and wnat to
> exploit the features support
> for packaging. In my features I have the following:
>
> <features>
> <feature name="YConX::Whiteboard" version="${project.version}">
>
> <!-- This line works for deploying into karaf, but not in conjunction with
> pax - exam -->
> <!--feature version="${project.version}">YConX::Equinox</feature-->
>
> <!-- TODO: avoid repetition of the derby version -->
> <bundle>mvn:org.apache.derby/derby/10.6.2.1</bundle>
> <bundle>mvn:${project.groupId}/${project.groupId}.core/${project.version}</bundle>
> <!--bundle>mvn:${project.groupId}/${project.groupId}.database/${project.version}</bundle>
> <bundle>mvn:${project.groupId}/${project.groupId}.dataproviderservice/${project.version}</bundle>
> <bundle>mvn:${project.groupId}/${project.groupId}.gui/${project.version}</bundle>
> <bundle>mvn:${project.groupId}/${project.groupId}.logger/${project.version}</bundle-->
> </feature>
> </features>
>
> For my integration test the first thing i want to test is that the packaging
> works ok and have copied/modified
> the FeaturesTest found in karaf itself. In my configuration I have:
>
> @Configuration
> public static Option[] configuration() throws Exception {
> return OptionUtils.combine(
> Helper.getDefaultOptions(
>
> systemProperty("org.ops4j.pax.logging.DefaultServiceLog.level").value("DEBUG")
> ),
> PaxRunnerOptions.scanFeatures(
>
> maven().groupId("de.yconx.osgi").artifactId("features").type("xml").classifier("features").version("0.0.1-SNAPSHOT"),
> "YConX::Equinox/0.0.1-SNAPSHOT"
> ),
> PaxRunnerOptions.scanFeatures(
>
> maven().groupId("de.yconx.whiteboard").artifactId("features").type("xml").classifier("features").version("0.0.1-SNAPSHOT"),
> "YConX::Whiteboard/0.0.1-SNAPSHOT"
> ),
> waitForFrameworkStartup(),
> equinox()
> );
> }
>
> The test succeeds if I omit the feature reference in my feature definition,
> but fails if i include it.
> The basic idea was, that the feature is my unit of deployment into the karaf
> container and that features
> kind of build on top of each other.
>
> So, the question is:
>
> Am I doing something out of the ordinary ?
> Am I hitting a pax-exam limitation that is already known? (happy to log a
> bug there...)
> Is there a syntax issue I am not spotting and would make it work in both
> environments ?
>
>
> Thanks in advance
> Andreas
>
>
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
