Louis CAD

Thanks for the report with the precise information! That name difference explains my questioning when I didn't see the local version but it worked when adding it manually.

@Savrov This is already supported. This issue is not about multi-module projects but about `includedBuilds`support, which is different.

I don't see how the version entry usage comments would be removed.

Hi @DanySK, thanks manifesting! I knew that it was a feature we don't currently support but was wondering if it'd actually bother anyone. I'll revisit this issue after #153 is...

@DanySK Are you aware of a way for a Gradle plugin to read the `content` from a repository? My research has been unsuccessful in finding a public API that allows...

I'm not talking about fetching the entirety of a repository, I'm talking about the `content` declaration you mentioned initially. Did you check the context when replying? About available versions, it's...

I'll do my best to ensure we never rely on a Gradle internal API because these are internals that can change and have no API stability guarantees, and I don't...

Versions from different repositories are already supported so long the maven coordinates are the same and the repositories are properly configured from Gradle.

refreshVersions looks in all the repositories configured for the module (including the dependencyResolutionManagement ones), and it'll mix versions from different repositories for the availability comments. Even GCS repos are supported.

I've seen I broke something with Kotlin plugin version by trying to fix something, I'll fix it on the main branch first.