multiPlatformProject and its contents are included via
includeBuild
.
Stuck on Kotlin 1.6.10 because of this.
I came across this super creative work-around to trick the IDE into thinking we're using 1.6.10 in order to keep it working, but it didn't do the trick for me.
Anyone else working around this issue?
Vitor Hugo Schwaab
08/26/2022, 8:03 PM
Opting-out of hierarchical project structure kinda works too.
But then, for whatever reason, Coroutines, KotlinxSerialization, KotlinxDatetime, and Ktor are the only dependencies that becomes unresolved, even though they have
enableCompatibilityMetadataVariant=true
.
n
Norbi
09/27/2022, 8:16 PM
May not be an option for you but I managed to "merge" two projects using symbolic links and some Gradle hackery :\