Ryan is right, the type is not correct.
See my previous mail about classifier and type.
Regards
JB
On 01/17/2014 04:02 PM, Ryan Moquin wrote:
What happens if in your unit test you execute a "feature:list" on Karaf
and make sure the feature xml is loaded? I could be wrong, but isn't
the pax-exam test container you are using meant for karaf 3.0.0?
In KarafIntegrationTestSupport near the buttom, this looks incorrect:
returnscanFeatures(getFeatureUrl("org.drools","drools-karaf-features").type("xml/features")
Type should be just xml right? "features" is the classifier. Maybe
that's your problem?
As a side note, the repository entry at the bottom of your itest pom can
be moved, it's redundant. I also wouldn't make your feature a test
dependency, just in case.
Ryan
On Fri, Jan 17, 2014 at 9:24 AM, Jean-Baptiste Onofré <[email protected]
<mailto:[email protected]>> wrote:
Could you try to "inject" the feature URL to Pax Exam with something
like:
@Configuration
public Option[] config() {
Option[] options = new Option[]{
keepRuntimeFolder(),
logLevel(LogLevelOption.__LogLevel.ERROR),
editConfigurationFileExtend("__etc/system.properties",
"my.feature.url",
maven().groupId("your").__artifactId("your").__versionAsInProject().__classifier("features").type("__xml").getURL()),
editConfigurationFileExtend("__etc/config.properties",
"org.apache.aries.blueprint.__synchronous", "true")
};
String debug = System.getProperty("debugMain"__);
if (debug != null) {
int l = options.length;
options = Arrays.copyOf(options, l + 1);
options[l] =
KarafDistributionOption.__debugConfiguration();
}
return options;
}
How do you install the feature ? using executeCommand ?
Did you add the feature in etc/org.apache.karaf.features.__cfg if
you don't use executeCommand ?
You can modify the etc/org.apache.karaf.features.__cfg in your
project and inject using editConfigurationFileExtend or Append (as I
did in my example).
Regards
JB
On 01/17/2014 10:19 AM, Charles Moulliard wrote:
Thx ;-)
On Fri, Jan 17, 2014 at 10:12 AM, Jean-Baptiste Onofré
<[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>> wrote:
Add the feature dependency in your pom. It's where Pax Exam is
looking for feature.
On 01/17/2014 09:27 AM, Charles Moulliard wrote:
Hi,
I experience a strange issue using pax-exam with Karaf
2.3.x
The following features file is available in my local
maven repo
mvn:org.drools/drools-karaf-____features/6.1.0-SNAPSHOT/xml/____features
-rw-r--r-- 1 chmoulli 1881291218 10473 Jan 17 08:45
/Users/chmoulli/.m2/____repository/org/drools/drools-____karaf-features/6.1.0-__SNAPSHOT/__drools-karaf-__features-6.1.0-__SNAPSHOT-__features.xml
but when pax-exam tries to find the features, I get ERRORS
(feature null
not found, feature drools-module not found, ...) from
FeaturesServiceImpl even if the features are well
present in
features file
example
<feature name="drools-module"
version="6.1.0-SNAPSHOT"
description="Drools core">
<feature
version="6.1.0-SNAPSHOT">____drools-common</feature>
<feature
version="6.1.0-SNAPSHOT">kie</____feature>
<bundle>mvn:org.drools/drools-____core/6.1.0-SNAPSHOT</bundle>
<bundle>mvn:org.drools/drools-____compiler/6.1.0-SNAPSHOT</____bundle>
<bundle>mvn:org.drools/drools-____osgi-integration/6.1.0-____SNAPSHOT</bundle>
</feature>
https://gist.github.com/____8470059
<https://gist.github.com/__8470059>
<https://gist.github.com/__8470059
<https://gist.github.com/8470059>>
Line 1133 -->
http://grepcode.com/file/____repo1.maven.org/maven2/org.____apache.karaf.features/org.____apache.karaf.features.core/2.____3.0/org/apache/karaf/__features/__internal/__FeaturesServiceImpl.__java
<http://grepcode.com/file/__repo1.maven.org/maven2/org.__apache.karaf.features/org.__apache.karaf.features.core/2.__3.0/org/apache/karaf/features/__internal/FeaturesServiceImpl.__java>
<http://grepcode.com/file/__repo1.maven.org/maven2/org.__apache.karaf.features/org.__apache.karaf.features.core/2.__3.0/org/apache/karaf/features/__internal/FeaturesServiceImpl.__java
<http://grepcode.com/file/repo1.maven.org/maven2/org.apache.karaf.features/org.apache.karaf.features.core/2.3.0/org/apache/karaf/features/internal/FeaturesServiceImpl.java>>
As this is really hard to debug Pax-Exam + Karaf, does
anybody
has an
idea bout the issue ? Could it be possible that
pax-exam does
not look
into my local repo ? Can I tell / force pax-exam to
look into my
local
repo ?
Regards,
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
<http://cmoulliard.github.io>
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
<http://cmoulliard.github.io>
--
Jean-Baptiste Onofré
[email protected] <mailto:[email protected]>
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
