Multi-module project dependencies are not resolved?

[serpro69]

It seems that (at least in some cases) dependencies between modules aren't resolved properly.

I have a buildSrc gradle plugin that is used by some submodules and that adds a dependency on another module: https://github.com/serpro69/kotlin-faker/blob/d804539e51f2ae1ff7d4f8255c83529b67a78b52/buildSrc/src/main/kotlin/faker-provider-conventions.gradle.kts#L29 and https://github.com/serpro69/kotlin-faker/blob/d804539e51f2ae1ff7d4f8255c83529b67a78b52/faker/books/build.gradle.kts#L2

Opening up the submodule results in unresolved references coming from the dependent module:

[strangepleasures]

Thanks for reporting! Support for bespoke Gradle configurations is limited at the moment. What we have now works well with static source sets and dependencies, but may result in incomplete imports when custom plugins are involved. We're working on a more mature solution on par with Gradle import in IntelliJ.

[serpro69]

Thanks @strangepleasures ,
Not expecting much from a pre-alpha plugin really :) Just wanted to report an issue that I discovered.