Hello,
I have a multi-module maven project (deployed to ServiceMix) and have recently
started a 'test' module to include integration tests for modules using Pax Exam.
To this aim, I am attempting to configure Pax Exam so that (all) dependencies
are included.
In effect, this means I have to completely replicate all the features/bundles
that are installed in ServiceMix, which could possibly be a list hundreds of
bundles long.
e.g.
@Configuration
public Option[] config() {
return options(
systemPackages("javax.jws", "javax.wsdl", ...etc);
mavenBundle("org.apache.cxf", "cxf-bundle", "2.4.3-fuse-03-02"),
// cxf-bundle transitive dependencies => rabbit hole
mavenBundle("org.apache.neethi", "neethi", "3.0.2"),
mavenBundle("xml-resolver", "xml-resolver", "1.2"),
// continue on for hundreds of lines? no thanks
junitBundles(),
equinox()
);
}
Since the transitive dependencies are a rabbit-hole, I would like to replace
this with a general mechanism for picking up the dependencies using maven.
One approach I have seen is to generate a dependencies properties file using a
plugin.
Typically this is used for the dependency versions. However, this is not good
enough - I want it to resolve *all* the dependencies, including the transitive
ones, from the pom file - is this possible?
I see that the scanFeatures(...) method is deprecated and only supported by the
Native Runner.
Any ideas for an approach, please?
Cheerio,
Nic
Nicholas Hemley
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
