Thanks to my colleague for collecting that information!!!
As he was preparing that; I wanted to dis-associate our stuff from the problem…
Here is a GitHub project with a sample: https://github.com/fwelland/Submarine
So the problem is there – but during the forum exchange we had earlier – I began to wonder if the group value was part of the ingredients used during dependency evaluation.
We publish to a private nexus and our artifacts belong to the same group (or so was the plan).
You’ll see our sample root build, sets that group for all subs.
Comment this line out, everything is OK; leave it in – that is when the chaos begins.
As you see, each build does make a distinct artifact jar file.
So maybe the inferred sub-project name (at leaf) + the group name is not unique and that is cause the substitution issue???
Not clear if this is the right or wrong thing for gradle to do, but it is unexpected.