Description of problem:

Currently the builder for EAP static module layers (kie-wb-distributions/kie-eap-integration) generates the dependencies between modules based on a descriptor file for each module. So the dependencies between generated EAP modules are defined manually.

This approach results difficult to maintain in a large application with a lot of third party resources, as the case of drools/jbpm. There are almost 40 modules to create.. so it's a difficult work to change and test the dependencies every time a developer changes or add some ones new (that occurs frequently due to we are on new releases development)

So this approach must be changed and simplified.

My idea is to define the static modules to create as maven modules too, then we can delegate to maven the creation of dependency graph completely. By this way we should avoid constant problems when developers are changing resources and its code.

The resulting dependency graph will show the dependencies between modules (considered maven resources too) and the resources that each module must contain.

This is the main idea but I have not completed this development yet, so I hope not having too much problems. If this approach will not be enough, then we must review all module dependencies in a manual way, but I hope to avoid this situation using this new approach or similar.

Version-Release number of selected component (if applicable):

6.0.0 / 6.1.0 (currently SNAPSHOT)

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

This bug is consequence of https://bugzilla.redhat.com/show_bug.cgi?id=1038713