The inability of using the desired version of an external dependency in the build script of a subproject in case another version of that dependency is loaded by the build script of the parent project causes subtle bugs that are very hard to track down. The issue is even less obvious if the parent project just transitively loads that dependency.
Would it be possible to detect such situations and display a warning?
The deceptive information shown by the buildEnvironment task is also problematic.
In any case it would be nice to at least document this behavior in the User Guide.