Improve behavior of the deploy goal for multi-module Maven projects

[hekonsek]

The issue has been reported here [1].

 projectA
    --projectB
    --projectC

what I want to achieve is to have one profile A which has B and C bundles inside.

So I define:

<properties>
  <fabric8.profile>A</fabric8.profile>
</properties>

in projectA's pom.

When I run mvn install I get correctly generated profile A in target of projectA, 
however I also have profile A generated in each of child projects, containing only bundles B and C         respectively.

When I run mvn fabric8:deploy on projectA it gets even worse, since profile A is deployed three     times, last time is from projectC - and then it contains only C bundle. 

Is it intended behaviour, a bug, or I just misconfigured the plugin? 

I think that defining Fabric8 plugin in the parent POM, should add all the bundles defined in the child modules to the profile - this might be a good idea. At least we should think more about the deploy goal in the context of the multi-module projects.

[1] https://groups.google.com/forum/#!topic/fabric8/K2HmwcsCx4A

[davsclaus]

Wonder if this question has relation to v2 as well?

[hekonsek]

No. Not relevant. Closing :) .