does anyone already have this situation when try to publish a Multiplatform library (JVM, Android an...
m
does anyone already have this situation when try to publish a Multiplatform library (JVM, Android and iOS) ?
Copy code
Reason: Task ':konnection:publishAndroidDebugPublicationToMavenRepository' uses this output of task ':konnection:signAndroidReleasePublication' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
p
Is a known issue
m
ok, is there a workaround?
p
val signingTasks = tasks.withType<Sign>() tasks.withType<AbstractPublishToMaven>().configureEach { dependsOn(signingTasks) }
a
m
nice, problem solved! thanks guys πŸ‘
a
btw
dependsOn(signingTasks)
means that the signing tasks for all publications will always be triggered, whether they are needed or not.
mustRunAfter(signingTasks)
should also fix it, but won't trigger tasks unnecessarily.
πŸ‘ 2