#535 kotlin 1.9.0, compose multiplatform 1.5.0 support

[Alex009]

Include changes from:

• Feature/issue 535 #565
• Fix #546 and #549 #561
• Configure plugin more lazily #547
• #530 fix task dependencies for gradle 8.2.1 #541

plugin reworked to Provider gradle's api to support dynamic changes of projects configuration.

---

If you have some not standard usecase - send PR with new sample project please. every sample project is our test case

---

This request contains breaking changes to better support dynamic changes of configurations and support new features in future (for example - configuration cache #311 ).

At first - resources directory moved from src/<resourceSourceSetName>/resources/MR to src/<sourceSetName>/moko-resources. I have multiple reasons for this:

1. Kotlin improve own resources directory management and Compose Multiplatform at now use content of resources directory. Our resources in MR directory was not ready for directly usage as resource - our resources if "source" for generation of platform resources. For example - for iOS all resources should be packed in bundle, for android svg should be converted to vector-xml. in resources source set in future we can put output of our generators, but "source" resources should not be copied into result app.
2. at gradle configuration stage we can't correctly decide what source set should be used for generation with current logic resourceSourceSetName that configured in plugin's extension - source sets can change at any time, and resourceSourceSetName in plugin extension can be changed in any time. So we should generate MR tasks for all sourcesets and decide what to do at EXECUTION stage. Also it allow to put resources in any sourceSet in hierarchy. For example in commonMain will be common resources and in iosMain will be ios specific resources added. It's was requested in Support for platform specific strings/resources #357

Second - MR object will be generated not only expect + actuals, but also for middle layer expects in different source sets. For example if we have next sourceSets hierarchy:

commonMain // here we have string common_hello
- androidMain // here no any additional strings
- appleMain  // here we have string apple_hello
-- iosMain  // here we have string ios_hello
--- iosX64Main  // here we have string iosx64_hello
--- iosSimulatorArm64Main // here no any additional strings
--- iosArm64Main // here no any additional strings

We can put resources in each source set. And as result we got this sources:
commonMain/MR.common.kt:

expect object MR {
    object strings: AppleMainStrings, IosMainStrings {
        val commonHello: StringResource
    }
}

expect interface AppleMainStrings // this naming not final. if you have idea about better name - please write comment
expect interface IosMainStrings // this naming not final. if you have idea about better name - please write comment

androidMain/MR.android.kt:

actual interface AppleMainStrings
actual interface IosMainStrings

actual object MR {
    actual object strings : AppleMainStrings, IosMainStrings {
        actual val commonHello: StringResource get() = TODO()
    }
}

appleMain/MR.apple.kt:

actual interface AppleMainStrings {
    val appleHello: StringResource
}

iosMain/MR.ios.kt:

actual interface IosMainStrings {
    val iosHello: StringResource
}

iosX64Main/MR.iosX64.kt:

actual object MR {
    actual object strings : AppleMainStrings, IosMainStrings {
        actual val commonHello: StringResource get() = TODO()
        override val appleHello: StringResource get() = TODO()
        override val iosHello: StringResource get() = TODO()
        val iosX64Hello: StringResource get() = TODO()
    }
}

iosArm64Main/MR.iosArm64.kt, iosSimulatorArm64Main/MR.iosSimulatorArm64.kt:

actual object MR {
    actual object strings : AppleMainStrings, IosMainStrings {
        actual val commonHello: StringResource get() = TODO()
        override val appleHello: StringResource get() = TODO()
        override val iosHello: StringResource get() = TODO()
    }
}

To decide what exactly should be generated each generateMR task will check own moko-resources directory and dependencies.
expect object MR will be located at lowest level of hierarchy (for example if we have not resources in commonMain but have in iosMain - expect will be in iosMain and commonMain will be empty. With this change we can remove resourcesSourceSet property from extension.

---

Current progress:

• Common generator
• Target generator
• Android MR generator
• JVM MR generator
• JS MR generator
• Apple MR generator
• Define generated resources as sourceSet, assets, resources**
• Copy resources of Apple and JS targets in KLibs**
• Metadata:
  • Base
  • All generators work with metadata
• Move resources from resources/MR to moko-resources
• Strings generator: - Success run on sample
  • Common target
  • Android target
  • Jvm target
  • Js target
  • Apple target
• Plurals generator: - Success run on sample
  • Common target
  • Android target
  • Jvm target
  • Js target
  • Apple target
• Files generator:
  • Common target
  • Android target
  • Jvm target
  • Js target
  • Apple target
• Fonts generator:
  • Common target
  • Android target
  • Jvm target
  • Js target
  • Apple target
• Assets generator:
  • Common target
  • Android target
  • Jvm target
  • Js target
  • Apple target
• Colors generator:
  • Common target
  • Android target
  • Jvm target
  • Js target
  • Apple target
• Images generator:
  • Common target
  • Android target
  • Jvm target
  • Js target
  • Apple target
• Testing on samples
• Testing on real IceRock projects

known issues:

• gradle task cache not invalidates when add resources in target sourceset, when project already compiled with resources exist on lower levels (when have resources in commonMain, compile, then create resources in desktopMain)
• fonts generated object is changed (in past we have additional object with font family name and inside have properties with styles. now we have only properties like fontfamily-style) - i think we can not fix this at all
• assets generated object is changed (in past was generated also inner objects like directory tree. now generated only flat properties and you can't see directory structure) - want to fix, but can't decide how (when we should generate interface for intermediate resources - we can't generated inner objects)
• in some cases actual for iOS target not generated

todo:

• research usage of Android Gradle Plugin Variants API to fix issues like Issue running check on 0.24.0-alpha01 #628
• try to implement integrational junit tests with testrun various kotlin, android gradle plugin versions - help required here
• check Action implementations - move all that can be moved to separated gradle tasks
• remove expect/actual interfaces at all (Parcelable usage, ResourceContainer, generated interfaces) - https://youtrack.jetbrains.com/issue/KT-59739
• fix assets bug - #535 kotlin 1.9.0, compose multiplatform 1.5.0 support #575 (comment)
• build failed with mockmp - #535 kotlin 1.9.0, compose multiplatform 1.5.0 support #575 (comment)
• js build failed - 0.24.0 alpha/beta #625 (comment)
• copyFrameworkResourcesToApp missed (when framework prefix is empty) - 0.24.0 alpha/beta #625 (reply in thread)
• android R class missed - 0.24.0 alpha/beta #625 (reply in thread)
• fix compatibility with compose resources - https://kotlinlang.slack.com/archives/CMC5LN42W/p1707978856036959?thread_ts=1705913203.842639&cid=CMC5LN42W
• check assets changes - https://kotlinlang.slack.com/archives/CMC5LN42W/p1707653155054129