Guys, I'm out of my depth here, maybe someone will...
# announcements
b
Guys, I'm out of my depth here, maybe someone will be able to help here. I have a MPP multi-module project, that worked fine with 1.4.0-M3, but after I update to 1.4.0, all modules that have dependencies on other modules do not build with attached error...
r
Does it work with
legacy
or
ir
setting (not
both
)?
b
Nope, tried with all three options
Oddly enough, a module in that project that does not depend on any other module builds fine
r
you could try updating gradle
b
Gradle is on 6.5
r
and perhaps you will find something in this thread: https://github.com/gradle/gradle/issues/12126
6.6.1 is available
and they are talking about 6.7 nightlies
b
hmm, 6.6.1 didn't help eiher 😕
i
There's a few changes you have to make to migrate to 1.4, I think you have to remove the
enableFeaturePreview("GRADLE_METADATA")
line in
gradle.settings
if you have it, among other things. Check this out https://kotlinlang.org/docs/reference/migrating-multiplatform-project-to-14.html
Thanks @Ivann Ruiz
👍 1
r
how it relates to your issue? it wasn't a 1.3 project, was it?
b
Yeah, it didn't solve it afterall. I was hoping that the only 1.3 dependency was causing it and after publishing that with 1.4 it'd solve the issue, but it didn't
@Robert Jaros don't you have any modules depending on other modules in kvision? Did you not face this issue?
r
I have, but no issues for me.
perhaps because my root module is not multiplatform
only a few submodules are mpp
but those submodules do have dependencies on other mpp submodules
Looking at how complicated the dependencies between these ~40 modules are (mpp depend on other mpp, and js depend on mpp), it's really amazing that it just worked without issues 😉
b
Oh well, i guess I'll just wait for 1.4.10 and hope they'll fix it.