Affects Version/s: 2.2, 2.2.2, 2.3
Fix Version/s: None
Number of attachments :
In two multi-module project setups like the ones attached to the bug where:
and another multi-module project with these characteristics:
The assembly zip in the child-aggregator/child-assembler project does not contain the jar from child-type1 even though it is in the reactor projects list...
I was able to trace the problem back to the class:
where the code reads:
If on the other hand (for working around the issue) one sets includeSubModules=false in the assembly definition (just uncomment in the "assembly-share" project assembly definition in the submitted example), then the reactor projects are used as per the top aggregator and everything goes well, except for the fact that another warning shows up saying that includeSubModules=false and useAllReactorProjects=true are incompatible and will be ignored (this combination is not ignored but the warning does make sense, though!)
This is related to the fact that in the child-aggregator project and modules, there is no dependency between the child-type1 project and the child-aggregator, which means the Reactor will order the builds as
child-type1, child-assembler, child-aggregator
but the code actually selects child-type1 as the "project" to determine modules from.