This message was deleted.

While I usually prefer to properly configure the projects to not need manual substitution rules, I'd say it should work, yes.

it doesn't seem to though. It syncs, so the gradle configuration is fine, but at build time it fails to locate "some.artifact.coordinates". If the pluginManagement

includeBuild

call is commented out, then there's no issue locating "some.artifact.coordinates" as a dependency

Maybe it is a bug. You should probably report it with a reproducer. And as workaround - or rather fix - remove the need for manual substitution

I'll see what I can do with that. Part of using manual substitution is that this included-build was a set of libraries and plugins that were more deeply integrated into the main project which are being prepared for extracting out to be a standalone set of libraries published via maven