Hello again, I am using the maven plugin and features service alone without other parts of Karaf so what I'm saying here is purely from observational perspective. I stopped using 2.x in the beginning because I didn't know how to override config.properties that by default included only system packages from jre-1.5.
Brian Topping wrote > > 2) Something that became more apparent is that test scope dependencies are > not filtered out of the feature generation for either version of the > plugin. Is this intentional? How does one generate a feature.xml without > the test dependencies? > The dependency resolution on 3.x relies on sonatype/eclipse aether instead of maven plugins capability of delivering dependenciens as artifacts so there is no direct relation to how maven handles dependencies (exclusion for instance). The only way I could produce something useful was to turn off transitive dependencies, because I do not understand the logic behind different scope and type (bundle/jar) combinations. This way I am able to leave out test scope dependencies that are not bundles (scope test: type jar=excluded, type bundle=included). Validation seems to have a bit different logic on how to handle dependencies and I already wrote my observation on that couple of threads ago. -- Tuomas -- View this message in context: http://karaf.922171.n3.nabble.com/Bundles-parameter-of-features-maven-plugin-generate-features-xml-tp3885138p3896255.html Sent from the Karaf - User mailing list archive at Nabble.com.
