I'm trying to create a KAR-archive of my application to be deployed to Karaf and for this I'm trying to generate the features.xml file using the generate-features-xml plugin.
However, I'm not entirely satisfied for the features.xml-file it generates. My project structure is roughly like this (X is my main application project): X-Feature X -> Depend on A and B and 3rd party bundles (some provided, some not) A -> Depend on B and 3rd party bundles (some provided, some not) B -> Depend on 3rd party bundles (some provided, some not) I would like to generate ultimately just a single feature : 'X' which has bundles A, B and some dependencies but not all as many are provided in the Karaf-setup (like CXF, Camel and ActiveMQ). When I run the features.xml-file generation, I get several features and I'm not quite sure about the logic in generating them. I do get a feature X that has bundle A as dependendy inside the <feature>-element and bundle B should also be inside the <feature>-element but for some reason a feature gets generated for it. Then I get a feature like jmockit, which we use in testing and some other features as well, which all are just transitive dependencies. I created the 'X-Feature' project just for creating the KAR-packaging and the features.xml-file and it has no source code, it has basically only dependency to bundle X on pom.xml and the generate-features-xml and create-kar plugin executions. I'd assume that I would get ONLY feature 'X' and dependencies as <bundle>-elements (excluding the provided ones) but that doesn't seem to be the case. Could you shortly explain the logic behind the generate-features-plugin? How does it determine WHAT features it generates? For example, what could be the reason that it generates B as a feature and not as a <bundle> inside feature X? I don't want multiple features, only one feature. -- View this message in context: http://karaf.922171.n3.nabble.com/Logic-behind-generate-features-xml-plugin-tp4027050.html Sent from the Karaf - User mailing list archive at Nabble.com.
