mirror of
https://github.com/bisq-network/bisq.git
synced 2025-02-23 06:55:08 +01:00
Problem: When merging #5824, the absence of this entry caused a build failure at dependency verification time against JDK11 and JDK15 on Ubuntu-latest [1]. It may also cause failures on other JDK/OS combinations, but the GitHub workflow was aborted before those failures couldhave occurred. In any case, this omission did not create build failures on any of the local development machines that tested the aforementioned PR. Reasons for this discrepancy are unknown. Solution: manually fetch the pom from [2], run `sha256sum` on it locally and commit the result to the verification metadata file. [1]: https://github.com/bisq-network/bisq/runs/4249640611?check_suite_focus=true#step:6:33 [2]: https://repo1.maven.org/maven2/com/fasterxml/jackson/jackson-base/2.11.1/jackson-base-2.11.1.pom |
||
---|---|---|
.. | ||
wrapper | ||
README.md | ||
verification-metadata.xml |
How to upgrade the Gradle version
Visit the Gradle website and decide the:
- desired version
- desired distribution type
- what is the sha256 for the version and type chosen above
Adjust the following command with tha arguments above and execute it twice:
./gradlew wrapper --gradle-version 6.6.1 \
--distribution-type all \
--gradle-distribution-sha256-sum 11657af6356b7587bfb37287b5992e94a9686d5c8a0a1b60b87b9928a2decde5
The first execution should automatically update:
bisq/gradle/wrapper/gradle-wrapper.properties
The second execution should then update:
bisq/gradle/wrapper/gradle-wrapper.jar
bisq/gradlew
bisq/gradlew.bat
The four updated files are ready to be committed.