I'm seeing this implicit dependency error with `va...

# gradle

[Oliver.O]

I'm seeing this implicit dependency error with `vanniktech/gradle-maven-publish-plugin`:

Some problems were found with the configuration of task ':testBalloon-gradle-plugin:signMavenPublication' (type 'Sign').
- Gradle detected a problem with the following location: '/Users/runner/work/testBalloon/testBalloon/testBalloon-gradle-plugin/build/libs/testBalloon-gradle-plugin-0.8.0-Beta1-sources.jar.asc'.

  Reason: Task ':testBalloon-gradle-plugin:publishPluginMavenPublicationToMavenCentralRepository' uses this output of task ':testBalloon-gradle-plugin:signMavenPublication' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

Is there a way to properly test this locally, invoking publishPluginMavenPublicationToMavenCentralRepository without actually publishing?

[Vampire]

Maybe use publish to maven local, or another local file-based repository and publish to that?

[Oliver.O]

These don't depend on signing, right?

[Bernd Prünster]

Had this ever since Gradle 8 with all our KMP projects. Our workaround: wire task dependencies manually. In addition, Kotlin 2.3 introduced some more dependencies between tasks that are not explicitly modelled, breaking CInterop, but we need to investigate further before we can file a proper report. Are your Kotlin 2.2 builds also affected?

[Oliver.O]

No, 2.2 was OK. But the cause seems to be a known Gradle bug: https://kotlinlang.slack.com/archives/C09FQGG85EC/p1766085944090469?thread_ts=1766084199.627669&channel=C09FQGG85EC&message_ts=1766085944.090469

[Rob Moore]

You could run the build in dry-run mode? (Use -m or —dry-run)

[CLOVIS]

https://youtrack.jetbrains.com/issue/KT-61858 ?

[Bernd Prünster]

Perfect! This is the issue i was looking for. Anybody want to bet when it will be fixed?

[CLOVIS]

Well it's already 2 years old, so probably not anytime soon

[Oliver.O]

You could run the build in dry-run mode? (Use -m or —dry-run)

No, I had tried that. It did not help. Now the problem has its workaround, so I don't need to try, but: You can probably test this locally by just invoking the Gradle publishAndReleaseToMavenCentral task. Without credentials, it will just fail when contacting Maven Central, but do everything up to that step, which should be sufficient to trigger the bug.

[Oliver.O]

For the record documenting it here. The underlying bug is with Gradle: https://github.com/gradle/gradle/issues/26091