Hi Massimo,

1. You can see the Maven plugin as a "substituter" for features repository XML templates. So, you can start with a XML template and replace dependency version or extend with this template based on the pom.xml. You don't have to use it, you can use a finalized XML directly. 2. It's related to the features XML generated: if the inner feature contains the prerequesite=true and dependency=true flags.

Regards
JB

On 11/13/2017 09:50 AM, Massimo Bono wrote:
Hello,

I've several questions about Karaf Maven Plugin, features-generate-descriptor goal; I hope you don't mind if I've put all of them in a single thread.

1)  I wonder why you couldn't declare feature dependencies inside the pom.xml. I know you need to declare them in a inputFile xml template (as I discovered both in http://karaf.922171.n3.nabble.com/Getting-the-plugin-to-generate-feature-dependencies-td4043053.html and in https://stackoverflow.com/questions/29645553/karaf-maven-plugin-defining-a-dependency-as-a-feature). However, I still don't grasp what is the underlying reason not to have them declared in the pom. I've looked at the code of the goal (on https://github.com/apache/karaf/blob/master/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/GenerateDescriptorMojo.java ) but I didn't fully understand the decision (probably because it's the first time I've looked into a Mojo). Why can't we have a "dependentFeature" tag? 2) Related to the first question: what is the purpose of "prerequisiteFeatures" and "dependencyFeatures" parameters?

Thanks for any kind reply!

--
*Ing. Massimo Bono*

--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to