Ensure signing tasks for different publication don't overwrite signatures

[wolfs]

When two publications contain the same file (like the main JAR), then the signing tasks for the publications will create the signatures in the same place. For example publishing to maven and ivy repositories in the same build causes the signature to be produced twice.

We shouldn't have tasks which produce the same files. A solution could be to have a signing task (artifact transform?) for each artifact, not for each publication.

---

cc: @gradle/execution

[stale]

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

[wolfs]

I think we should fix this.

[vlsi]

Here's a workaround:

// Workaround for https://github.com/gradle/gradle/issues/15568
tasks.withType<AbstractPublishToMaven>().configureEach {
    mustRunAfter(tasks.withType<Sign>())
}