Closed d-bytebase closed 11 months ago
Thank you for your contribution, but I had to revert the changes because it started causing problems with releasing.
There is an error message from the log (logs_320.zip):
FAILURE: Build failed with an exception.
* What went wrong:
Some problems were found with the configuration of task ':alpine-platforms:signArm32v6AlpinePublication' (type 'Sign').
- Gradle detected a problem with the following location: '/home/runner/work/embedded-postgres-binaries/embedded-postgres-binaries/alpine-platforms/build/libs/embedded-postgres-binaries-16.1.0-javadoc.jar.asc'.
Reason: Task ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository' uses this output of task ':alpine-platforms:signArm32v6AlpinePublication' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:
1. Declare task ':alpine-platforms:signArm32v6AlpinePublication' as an input of ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository'.
2. Declare an explicit dependency on ':alpine-platforms:signArm32v6AlpinePublication' from ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository' using Task#dependsOn.
3. Declare an explicit dependency on ':alpine-platforms:signArm32v6AlpinePublication' from ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository' using Task#mustRunAfter.
For more information, please refer to https://docs.gradle.org/8.4/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.
- Gradle detected a problem with the following location: '/home/runner/work/embedded-postgres-binaries/embedded-postgres-binaries/alpine-platforms/build/libs/embedded-postgres-binaries-16.1.0-sources.jar.asc'.
Reason: Task ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository' uses this output of task ':alpine-platforms:signArm32v6AlpinePublication' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Possible solutions:
1. Declare task ':alpine-platforms:signArm32v6AlpinePublication' as an input of ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository'.
2. Declare an explicit dependency on ':alpine-platforms:signArm32v6AlpinePublication' from ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository' using Task#dependsOn.
3. Declare an explicit dependency on ':alpine-platforms:signArm32v6AlpinePublication' from ':alpine-platforms:publishAmd64AlpinePublicationToMavenRepository' using Task#mustRunAfter.
For more information, please refer to https://docs.gradle.org/8.4/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.
Hi @kornholi, would you help take a look? Thanks!