Gradle Config Cache

KMMBridge supports Gradle configuration cache. However, there are some cases where config cache is not supported.

Maven Publishing

The MavenPublishArtifactManager does not support Gradle configuration cache due to a bug with the Gradle Maven plugin. When that is resolved, this restriction should be fixed. Our tracking issue for reference.

However, by default, KMMBridge skips publishing-related configuration if not explicitly enabled. As a result, you can have config cache enabled for development, and disable it for CI builds by passing a Gradle parameter on the command line:

./gradlew kmmBridgePublish -PENABLE_PUBLISHING=true -Porg.gradle.configuration-cache=false (Etc)

Setup Deploy Keys

To support cross-repo publishing with GitHub, KMMBridge provides the setupDeployKeys Gradle task. This task is only used during setup. It will run successfully, but Gradle will end with an error if config cache is enabled. You can safely ignore this error.