Hi Jean-Baptiste, yes, I (and Reto) know we can use feature.xml templates. But that is not what you want in a "POM first" project. The POM is supposed to be the single source for dependency information, artifact declarations, etc.. Feature dependencies are just another flavor of dependency, and it would be very nice if the plugin could resolve them for the feature.xml artifact. Otherwise there is duplication of project meta data, is there not? A dependency feature is normally also a compile time dependency. At least in my case it is. So the same dependency would have to be maintained in the POM and the feature.xml template.
As a side question: Do you happen to know if the Camel feature.xml is maintained manually as well? I noticed that it is incredibly "lean" and does not state a lot of its actual dependencies. My assumption is that the knowledge of what bundles are installed in a stock Karaf installation is worked into that feature file. If my assumption is correct, is there a way to pull that knowledge into a Maven project by means of a meta-dependency? So with tool support one could easily find out what dependencies one carries unnecessarily/are provided if the runtime-container is Karaf? If the assumption is wrong, how does it work? Regards, Ralf -- View this message in context: http://karaf.922171.n3.nabble.com/karaf-maven-plugin-and-dependent-features-tp4029629p4035756.html Sent from the Karaf - User mailing list archive at Nabble.com.
