Good day! :slightly_smiling_face: I am stuck with ...

# server

[Gillian Buijs]

Good day! 🙂 I am stuck with a dependency problem and hope someone here can help me out. I have a mono repo consisting of 5 modules. Each module is an independent Gradle project (has its own settings.gradle.kts and build.gradle.kts etc) and may or may not have included sub modules. Some of these modules are KMP projects and some or plain Java. Some modules depend on another module in this mono repo, which is always resolved by publishing the artifact to a private repo and pulling it from there. Okay so next I have an example project which uses a module from this mono repo. When I implement a module and sync the project I get this error: """Dependency resolution has ignored the cycle to produce a result. It is recommended to resolve the cycle by upgrading one or more dependencies.
Detecting cycle in external variants for :
dev.buijs.klutterannotations kmp0.2.12:
- app-backendcommon1.0""".... I'm totally baffled because this module (annotations-kmp) literally has zero dependencies. I have by now also removed every single other dep implementation in the example project. I also backtracked every package and artifact name to make sure they are all unique (hence annotations-jvm, annotations-kmp)... Source is here: https://github.com/buijs-dev/klutter

[Gillian Buijs]

I think this might be a bug because when I change the KMP module to a Java module, the exception is gone and importing works correctly. Unfortunately you can't import a Java lib in a KMP lib...

[Gillian Buijs]

Yup it's a bug. Downgrading from Gradle 7 to 6.7.1 fixed the issue.