You may want to revert this swapping in of the 17.1 versions of the modules. I suggested it in the vain hope that it might produce some kind of "ah ha!", but it has not. It seems there must be some difference between the two versions given that the behavior is different, but I fear that this hacked up investigation may produce more questions than it answers.

We generally make a separate api jar for a module if another module depends on it (which is where the depProjectConfig: apiCompile comes from), but that is really a compile-time thing, not a run-time thing unless I'm forgetting something about the class loaders.

Susan