Ecosystem/haveno
Ecosystem/haveno
1
0
Fork 0
mirror of https://github.com/haveno-dex/haveno.git synced 2024-11-16 15:58:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
haveno/gradle/verification-metadata.xml

3646 lines
221 KiB
XML
Raw Normal View History

replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<?xml version="1.0" encoding="UTF-8"?>
Upgrade Gradle wrapper to 8.5
2023-12-13 20:59:14 +00:00
<verification-metadata xmlns="https://schema.gradle.org/dependency-verification" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://schema.gradle.org/dependency-verification https://schema.gradle.org/dependency-verification/dependency-verification-1.3.xsd">
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<configuration>
<verify-metadata>false</verify-metadata>
<verify-signatures>false</verify-signatures>
<trusted-artifacts>
<trust file=".*-javadoc[.]jar" regex="true"/>
<trust file=".*-sources[.]jar" regex="true"/>
</trusted-artifacts>
</configuration>
<components>
<component group="aopalliance" name="aopalliance" version="1.0">
<artifact name="aopalliance-1.0.jar">
<sha256 value="0addec670fedcd3f113c5c8091d783280d23f75e3acb841b61a9cdb079376a08" origin="Generated by Gradle"/>
</artifact>
<artifact name="aopalliance-1.0.pom">
<sha256 value="26e82330157d6b844b67a8064945e206581e772977183e3e31fec6058aa9a59b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="ch.qos.logback" name="logback-classic" version="1.1.11">
<artifact name="logback-classic-1.1.11.jar">
<sha256 value="86a0268c3c96888d4e49d8a754b5b2173286aee100559e803efcbb0df676c66e" origin="Generated by Gradle"/>
</artifact>
<artifact name="logback-classic-1.1.11.pom">
<sha256 value="936d197f26ed8df79b5e0a8f31772924ef864162dcb5fbc82b15e02dc054b1bd" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="ch.qos.logback" name="logback-classic" version="1.2.10">
<artifact name="logback-classic-1.2.10.jar">
<sha256 value="3160ae988af82c8bf3024ddbe034a82da98bb186fd09e76c50543c5b9da5cc5e" origin="Generated by Gradle"/>
</artifact>
<artifact name="logback-classic-1.2.10.pom">
<sha256 value="4accd4aa1c65d1acc70e6c391ab1033f5276b6e08628f1699d429aa4c3d5b884" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="ch.qos.logback" name="logback-core" version="1.1.11">
<artifact name="logback-core-1.1.11.jar">
<sha256 value="58738067842476feeae5768e832cd36a0e40ce41576ba5739c3632d376bd8c86" origin="Generated by Gradle"/>
</artifact>
<artifact name="logback-core-1.1.11.pom">
<sha256 value="7199197992fb549a4b620f368a6726298360eb9ebb37e4ed16eb4e5ad2be0f25" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="ch.qos.logback" name="logback-core" version="1.2.10">
<artifact name="logback-core-1.2.10.jar">
<sha256 value="ba51a3fe56691f9dd7fe742e4a73c3ab4aaaa32202c73409ba56f18687399a08" origin="Generated by Gradle"/>
</artifact>
<artifact name="logback-core-1.2.10.pom">
<sha256 value="1d32cf679d8780d7c9c915e6cc5db431d5b40c2aedc58a84a17cd023e1f0d09c" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="ch.qos.logback" name="logback-parent" version="1.1.11">
<artifact name="logback-parent-1.1.11.pom">
<sha256 value="ec6a3b1ccb21e66c02e36899735c0c2171c5bd3a4ea269a28be95f9f2e8a822b" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="ch.qos.logback" name="logback-parent" version="1.2.10">
<artifact name="logback-parent-1.2.10.pom">
<sha256 value="ccbd8e06a67f765a1a2498a7076032ce366420c2129d680bd302633572cab354" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.auth0" name="java-jwt" version="3.10.0">
<artifact name="java-jwt-3.10.0.jar">
<sha256 value="dc5a83714568d955181c8f5cf9ea634573eb2fde426e05a2b1b92d2d74b86acf" origin="Generated by Gradle"/>
</artifact>
<artifact name="java-jwt-3.10.0.pom">
<sha256 value="3e1e9d97cb5aaa14813a526bf259bbf4cd6b7eddee1a08dfc802fc4ef67094f1" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="com.auth0" name="java-jwt" version="3.18.3">
<artifact name="java-jwt-3.18.3.jar">
<sha256 value="e51e9c0237ca4a27b80e603081dab80e43f3847020ea1b57292df3e0d11d17db" origin="Generated by Gradle"/>
</artifact>
<artifact name="java-jwt-3.18.3.pom">
<sha256 value="f4e46a0910c9d2bba77f906fcf7686ed8b10817c4d9acb58251ccdc1a71dfacf" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.datastax.oss" name="java-driver-bom" version="4.13.0">
<artifact name="java-driver-bom-4.13.0.pom">
<sha256 value="5a7ede4c787baa9bf68ca309ab8673f32fcf1fa59b493dfba7465b9c5060a700" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.eatthepath" name="fast-uuid" version="0.1">
<artifact name="fast-uuid-0.1.jar">
<sha256 value="670976cae3f41609128f647388791f43af361f3e7403ef0e3f0529c23fa1bccc" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml" name="classmate" version="1.3.4">
<artifact name="classmate-1.3.4.jar">
<sha256 value="c2bfcc21467351d0f9a1558822b72dbac2b21f6b9f700a44fc6b345491ef3c88" origin="Generated by Gradle"/>
</artifact>
<artifact name="classmate-1.3.4.pom">
<sha256 value="d8e7f6d146289aca1477195e67bb4b7be5f29bbbb5f804198d03cfba92fd8490" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml" name="oss-parent" version="24">
<artifact name="oss-parent-24.pom">
<sha256 value="e3809d58570390c327efe56587d8dea3caa53186b91875e0b36226e08211f05a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml" name="oss-parent" version="27">
<artifact name="oss-parent-27.pom">
<sha256 value="b9b8f388fd628057b1249756468b86726c8fd5816ce14d313cb40003a509beeb" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.fasterxml" name="oss-parent" version="43">
<artifact name="oss-parent-43.pom">
<sha256 value="e5585cc1c37079b2e3817a8997945736f158831844d59d0e4d3a45b27611f926" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson" name="jackson-base" version="2.13.1">
<artifact name="jackson-base-2.13.1.pom">
<sha256 value="1ef88d9f41d0cb8ea074fb2171939eb94db2ebe17f055bdd147f8ae051bb9c95" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson" name="jackson-bom" version="2.13.1">
<artifact name="jackson-bom-2.13.1.pom">
<sha256 value="5a539c2596d5b7fcf0aba0a08214ce0fa6937b3ed1534fc1a70a9487a394bcb5" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson" name="jackson-parent" version="2.13">
<artifact name="jackson-parent-2.13.pom">
<sha256 value="2bba89978172af1effcb4d143d09921a3f3082ca4dcf122b1ded98bf55b2ad57" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson.core" name="jackson-annotations" version="2.13.1">
<artifact name="jackson-annotations-2.13.1.jar">
<sha256 value="ab607939d288e22bff4cb97acc6b25e841d82681f2bc40ce67bb35cb0ffdb06d" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-annotations-2.13.1.pom">
<sha256 value="28b24c6959198210ccb22908d47ef905a6f9235bb8afad60e888e7c4698865a6" origin="Generated by Gradle"/>
</artifact>
</component>
update to monero-java v0.7.6 to fix jackson dependency
2022-10-14 02:28:51 +00:00
<component group="com.fasterxml.jackson.core" name="jackson-annotations" version="2.13.2">
<artifact name="jackson-annotations-2.13.2.jar">
<sha256 value="7d3df5aafa2dc61ad1dbad30f411548c0184ed92d94628c63168721f08237cd4" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
<component group="com.fasterxml.jackson.core" name="jackson-core" version="2.1.3">
<artifact name="jackson-core-2.1.3.jar">
<sha256 value="754184022345800c2d066eceeaf2f7a88a7c2aaeae23eb1c76ef598854aa9157" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.fasterxml.jackson.core" name="jackson-core" version="2.13.1">
<artifact name="jackson-core-2.13.1.jar">
<sha256 value="8be6935cd8f9673ac684a589aaa1caecd57dee7c37ed1443d17924325799003d" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-core-2.13.1.pom">
<sha256 value="64fec520456c5dafe0ba940564946304fba6117068b5adf33662b10035fafe74" origin="Generated by Gradle"/>
</artifact>
</component>
update to monero-java v0.7.6 to fix jackson dependency
2022-10-14 02:28:51 +00:00
<component group="com.fasterxml.jackson.core" name="jackson-core" version="2.13.2">
<artifact name="jackson-core-2.13.2.jar">
<sha256 value="9bfa278ad05179fb68087851caf607652702ca25424bec8358a3716e751405c8" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.fasterxml.jackson.core" name="jackson-databind" version="2.13.1">
<artifact name="jackson-databind-2.13.1.jar">
<sha256 value="56cfbdc9e1736b5c56b43757f6cf546ee6d49393c79383c4e495c4f7047cb506" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-databind-2.13.1.pom">
<sha256 value="3c8ec4b3d5984bc86bc30da9ed86b35c34d3d68af9decf400c35893ad24f58ae" origin="Generated by Gradle"/>
</artifact>
</component>
update to monero-java v0.7.6 to fix jackson dependency
2022-10-14 02:28:51 +00:00
<component group="com.fasterxml.jackson.core" name="jackson-databind" version="2.13.2">
<artifact name="jackson-databind-2.13.2.jar">
<sha256 value="0d5459b7f18184c4ce8f07264b1b7feced51529e550a098d6f9e2dfe091138ad" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.fasterxml.jackson.datatype" name="jackson-datatype-jdk8" version="2.13.1">
<artifact name="jackson-datatype-jdk8-2.13.1.jar">
<sha256 value="8fd36efc6cbda4f3f22400c1ea0d07f043fc0b8b80c9e3e4142b82e702b51118" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-datatype-jdk8-2.13.1.pom">
<sha256 value="a82a05aa1427d5ec7ba6b229adf679d7ceeeb6d4f495bd4f5155138bd72472a1" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson.datatype" name="jackson-datatype-jsr310" version="2.13.1">
<artifact name="jackson-datatype-jsr310-2.13.1.jar">
<sha256 value="0219a9a4c1b983031111dc87e6edc8d1c6b5997581ac2ac20c4ffe6509adb605" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-datatype-jsr310-2.13.1.pom">
<sha256 value="9267d72b3cd97b41682df569b7eb5268f50108ddd63f61c62e5b0eb36536b574" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson.module" name="jackson-module-jaxb-annotations" version="2.13.1">
<artifact name="jackson-module-jaxb-annotations-2.13.1.jar">
<sha256 value="b717db30f0bc14ad6545d2620468fe7fd9ceded0a09f639f35fac7f40e075e4c" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-module-jaxb-annotations-2.13.1.pom">
<sha256 value="a75f536ece8eb298f648aa0738099d9494b75123ddeba141440bcbfdda9d27ea" origin="Generated by Gradle"/>
</artifact>
</component>
update to monero-java v0.7.6 to fix jackson dependency
2022-10-14 02:28:51 +00:00
<component group="com.fasterxml.jackson.module" name="jackson-module-jaxb-annotations" version="2.13.2">
<artifact name="jackson-module-jaxb-annotations-2.13.2.jar">
<sha256 value="7fdf1769b4feddbd73d89da47dc07b2e8230860700da00885a92bf7d66205376" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.fasterxml.jackson.module" name="jackson-module-parameter-names" version="2.13.1">
<artifact name="jackson-module-parameter-names-2.13.1.jar">
<sha256 value="6deafd562297685e748cdb44ceef0d8853eec30859b18c7f7021747b44be5e67" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-module-parameter-names-2.13.1.pom">
<sha256 value="f9385ea7fbe6d3731aa965eff11cc4c1e94ea00a1265c2cc1ba605d7010ebfcd" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson.module" name="jackson-modules-base" version="2.13.1">
<artifact name="jackson-modules-base-2.13.1.pom">
<sha256 value="bbf09eb6177793218eec17171631a09c145f3eafee68b1153aade38dad0cbdba" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.fasterxml.jackson.module" name="jackson-modules-java8" version="2.13.1">
<artifact name="jackson-modules-java8-2.13.1.pom">
<sha256 value="b7774955491262076d4fec12de392628a541e0560018142a0a6e38f72bb96010" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.JesusMcCloud" name="jtorctl" version="9b5ba2036b">
<artifact name="jtorctl-9b5ba2036b.jar">
<sha256 value="b2bdfe9758e4c82ff1b10e7c3098981bf55ea3e5f161ee7990ac125003a6cdbe" origin="Generated by Gradle"/>
</artifact>
<artifact name="jtorctl-9b5ba2036b.pom">
<sha256 value="218fbc37a57bcf888af917220c31acea39197859cc47519c12f1151fa4a27812" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network" name="bitcoinj" version="2a80db4">
<artifact name="bitcoinj-2a80db4.jar">
<sha256 value="65ed08fa5777ea4a08599bdd575e7dc1f4ba2d4d5835472551439d6f6252e68a" origin="Generated by Gradle"/>
</artifact>
<artifact name="bitcoinj-2a80db4.pom">
<sha256 value="bd2ab2cb062409cad85d16fb93dce99701d1b6de66a5a76f4b30d6c438568e2f" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network" name="jsocks" version="43b004b5bcc468fb1213767853e1d8a54fd4a359">
<artifact name="jsocks-43b004b5bcc468fb1213767853e1d8a54fd4a359.jar">
<sha256 value="8ff45a70a9a927427618bfe6dab80b06a054f3da8addbad2f4228d0ab9cc03f6" origin="Generated by Gradle"/>
</artifact>
<artifact name="jsocks-43b004b5bcc468fb1213767853e1d8a54fd4a359.pom">
<sha256 value="6831518f5f2b48cf63f3e8e6c43d12fd6dc1457f18ca61a5c87b20e43b4022a7" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network" name="jsonrpc4j" version="1.6.0.bisq.1">
<artifact name="jsonrpc4j-1.6.0.bisq.1.jar">
<sha256 value="842b4a660440ef53cd436da2e21c3e1fed939b620a3fc7542307deb3e77fdeb6" origin="Generated by Gradle"/>
</artifact>
<artifact name="jsonrpc4j-1.6.0.bisq.1.pom">
<sha256 value="3cab07703f2ac8fa233bc7f35a8816b65a9f2b04a1b7f84cb8e147c1b45f5cfa" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network" name="jtorctl" version="b2a172f44edcd8deaa5ed75d936dcbb007f0d774">
<artifact name="jtorctl-b2a172f44edcd8deaa5ed75d936dcbb007f0d774.jar">
<sha256 value="3da480f9e161879529d81a30bb0b2f168c61ec59f50d1c0a1930389721301028" origin="Generated by Gradle"/>
</artifact>
<artifact name="jtorctl-b2a172f44edcd8deaa5ed75d936dcbb007f0d774.pom">
<sha256 value="d4ea711258c783e0accb8feaaa204f0414781551b0159fa17e5f1869200f96f7" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.netlayer" name="parent" version="0.7.2">
<artifact name="parent-0.7.2.pom">
<sha256 value="b79a930b3bc987f1be5821362792b23bb430eb6645b282ca99f4d53a85ef9a6f" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.netlayer" name="parent" version="6797461310f077bbea4f43a3a509c077b0ed8c34">
<artifact name="parent-6797461310f077bbea4f43a3a509c077b0ed8c34.pom">
<sha256 value="d6403c9c26d26ba3ee58f971a5b094522c38ac499940e7181c70e06711ab68f1" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.netlayer" name="parent" version="8db4a13">
<artifact name="parent-8db4a13.pom">
<sha256 value="c0460cf420ac504a3b5349bd91f6a4bba3534ab7be43e2639bb081b032e5e602" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.netlayer" name="tor" version="0.7.2">
<artifact name="tor-0.7.2.jar">
<sha256 value="48b097d756bf1221a2fe7f9bfd4ec6c505719502997d87cc18d912d4323e59d3" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-0.7.2.pom">
<sha256 value="6306d89cfdb12bd0b6436390de71cef31879985da10d071a3bdad56bf287bbbb" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.netlayer" name="tor" version="6797461310f077bbea4f43a3a509c077b0ed8c34">
<artifact name="tor-6797461310f077bbea4f43a3a509c077b0ed8c34.jar">
<sha256 value="1536211d3f204059e2ad49c136978b36ebaa19e62103fcd46dcb926842fa0718" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-6797461310f077bbea4f43a3a509c077b0ed8c34.pom">
<sha256 value="7a0ccbecf1471f6be02fb034c006e36b7a6fd249544521c653fed09fbbcec0b1" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.netlayer" name="tor" version="8db4a13">
<artifact name="tor-8db4a13.jar">
<sha256 value="37198bc56e8fe112f8c80441544a2b9731929dae586bda841a4a926fdc04f457" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-8db4a13.pom">
<sha256 value="d1cb5d57710c43642771681d8b1c9039c722fb949bdc5a2022389f5a81501f42" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.netlayer" name="tor.external" version="0.7.2">
<artifact name="tor.external-0.7.2.jar">
<sha256 value="45daf9b30f753c49b62cf56226539e824886ce1ff430e03dbef1bddff919cbfc" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.external-0.7.2.pom">
<sha256 value="605e15f473aa7163c4dfa75b0fa17a96466d24c6e3d7a66925b29aadde98dfb4" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.netlayer" name="tor.external" version="6797461310f077bbea4f43a3a509c077b0ed8c34">
<artifact name="tor.external-6797461310f077bbea4f43a3a509c077b0ed8c34.jar">
<sha256 value="d79dee1380fcc912dd9f321e6689b99129a90c6b30085b3f86a0b81830ecee71" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.external-6797461310f077bbea4f43a3a509c077b0ed8c34.pom">
<sha256 value="949ab51a912ba5c126ffda083da2f0366bc9eda36afc5358183e040fee24d86f" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.netlayer" name="tor.external" version="8db4a13">
<artifact name="tor.external-8db4a13.jar">
<sha256 value="e1d6b8fe73891207701c6b14317be789fd4acd25f7b499425d2471598d9a22ac" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.external-8db4a13.pom">
<sha256 value="11918499210e0c12e9d517596eedb34b897021686cf8a1efd8ea87ae3b7e184d" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.netlayer" name="tor.native" version="0.7.2">
<artifact name="tor.native-0.7.2.jar">
<sha256 value="ebb37e76fa14461be1ab2750daa3f8e5b78c8ff0d2adb72832ca0d38a1fb8f0d" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.native-0.7.2.pom">
<sha256 value="021ab6d438023653afee96c0fab1262eed6b7522fce76e114593d55e6d7d9928" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.netlayer" name="tor.native" version="6797461310f077bbea4f43a3a509c077b0ed8c34">
<artifact name="tor.native-6797461310f077bbea4f43a3a509c077b0ed8c34.jar">
<sha256 value="7ab70a9948fffea33da9fee161c5783a74aeb1531e3fda09995c47bb5e2de0f5" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.native-6797461310f077bbea4f43a3a509c077b0ed8c34.pom">
<sha256 value="17ba4bb22d00441e286dde286045d68190003e849f49871bdac96a5b41478533" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.netlayer" name="tor.native" version="8db4a13">
<artifact name="tor.native-8db4a13.jar">
<sha256 value="aa3edf9c27071fdc2b7d55b00dbc7c6cd5dc9aa9f87aafa4be0805f818a466be" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.native-8db4a13.pom">
<sha256 value="13e497b9fa97fc994e907aaad69ed81c5433380887a8ac7237bc18e8da48683b" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary" version="6d1fd95">
<artifact name="tor-binary-6d1fd95.pom">
<sha256 value="ac20fe51c6473ecaa440458c8255294ff2b30cfed45918527742315bb3d74a86" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary" version="787183b147286d783a6392bb9ffcd8ba920d6fff">
<artifact name="tor-binary-787183b147286d783a6392bb9ffcd8ba920d6fff.pom">
<sha256 value="4e127121fefb50fed62a83d5fbd31064b9f16f1a528571675e0ec3042376dab3" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary" version="b9c6227">
<artifact name="tor-binary-b9c6227.pom">
<sha256 value="f1ef0c2b2a1df585f057b96b62b05e2e7d7953353b64e29ac798810ff2919b42" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-geoip" version="6d1fd95">
<artifact name="tor-binary-geoip-6d1fd95.jar">
<sha256 value="5a55df3a5bed0aa57165e9bae9ecda8b14d5e85b97dd1a266fa77602fbdaec54" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-geoip-6d1fd95.pom">
<sha256 value="14fbcfc4de8e07b8c5bf7c1e279704905cc98795e7460cf558288ce1eaaf1927" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-geoip" version="787183b147286d783a6392bb9ffcd8ba920d6fff">
<artifact name="tor-binary-geoip-787183b147286d783a6392bb9ffcd8ba920d6fff.jar">
<sha256 value="e1f0a9708ad5fc5373db84fb14570d36eff842eb71e99c0930db64617604a2bf" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-geoip-787183b147286d783a6392bb9ffcd8ba920d6fff.pom">
<sha256 value="a6f45951fb73b57c9ac37d389f5adcfecde5f06c2e50d1a8381e640261e5a6b5" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-geoip" version="b9c6227">
<artifact name="tor-binary-geoip-b9c6227.jar">
<sha256 value="cfefbf2d8591b5dd321ec17a02a3682d21763cf50525fa5496c9ec8968413c4e" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-geoip-b9c6227.pom">
<sha256 value="197d034216b332fcfaa7111442ac4a23bddc60fb71fefba1c736fe9844c1001b" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux32" version="6d1fd95">
<artifact name="tor-binary-linux32-6d1fd95.jar">
<sha256 value="fe8b0ddb1c109b453adf9b055e067be04b6ca4cda9d2b33c875b99d2092f0eae" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux32-6d1fd95.pom">
<sha256 value="0ae70e17d9566c88204d02de32c1646d672e78711da97124d23fd397a1da9d13" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux32" version="787183b147286d783a6392bb9ffcd8ba920d6fff">
<artifact name="tor-binary-linux32-787183b147286d783a6392bb9ffcd8ba920d6fff.jar">
<sha256 value="b1e8b3f83b08c839a4282a32ef75be69db3ec3061b3472e367606782b861cb55" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux32-787183b147286d783a6392bb9ffcd8ba920d6fff.pom">
<sha256 value="4166e686e18b875fe09e34e19ea294a5841b9d0354072e60fb7779b813c9ff45" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux32" version="b9c6227">
<artifact name="tor-binary-linux32-b9c6227.jar">
<sha256 value="b82b6595f78ef52a44e58000fe5d7f679681739451872f5bbd123e5dbd2af050" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux32-b9c6227.pom">
<sha256 value="a01902c476556a0529413b0f3810e954a5eb8a7cdc1a9cc604ec2d24ceca91ce" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux64" version="6d1fd95">
<artifact name="tor-binary-linux64-6d1fd95.jar">
<sha256 value="7f58d31dd684b2e361e2980ba23922cadd5d9d8f8dbab9b3a2c6737741b21f7e" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux64-6d1fd95.pom">
<sha256 value="48f0435519eae6ff6af88656a64502320befc392b2c5d59ac2fb47412c9ba52d" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux64" version="787183b147286d783a6392bb9ffcd8ba920d6fff">
<artifact name="tor-binary-linux64-787183b147286d783a6392bb9ffcd8ba920d6fff.jar">
<sha256 value="4e956beca59ffce771d0fa40a0b20181c3531d278ff0f1d474a378c0fa9bc76b" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux64-787183b147286d783a6392bb9ffcd8ba920d6fff.pom">
<sha256 value="1f98896ea3822644bebd3c3278497684504e291df03531bf72f072ab2d6b44a1" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux64" version="b9c6227">
<artifact name="tor-binary-linux64-b9c6227.jar">
<sha256 value="d5c1d54b2c2323ac1124435be633c7822a28e6fe9160486d03102cc2b444df24" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux64-b9c6227.pom">
<sha256 value="ee305ee12585057bcce380710e4a5ae3a3ed43e1701f5e565f15b75854e3e715" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-macos" version="6d1fd95">
<artifact name="tor-binary-macos-6d1fd95.jar">
<sha256 value="a23802ff66d4ac01366ebe712879e2f51df960572dc34db269588da87453a70d" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-macos-6d1fd95.pom">
<sha256 value="0c1b6633882ca625f50c78b960714baa81ef286b5dfc26886145f7960feab738" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-macos" version="787183b147286d783a6392bb9ffcd8ba920d6fff">
<artifact name="tor-binary-macos-787183b147286d783a6392bb9ffcd8ba920d6fff.jar">
<sha256 value="9b4114bd7699951dc6b04a10398bd6acc17a966db48c7fa79e302cc0b6fe7ecf" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-macos-787183b147286d783a6392bb9ffcd8ba920d6fff.pom">
<sha256 value="6b8f372ac6dc38c06575612cc00f5e6d804d80dfe761f8ca0d1aa4562da9d2dd" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-macos" version="b9c6227">
<artifact name="tor-binary-macos-b9c6227.jar">
<sha256 value="6216d66241e020fec1a55648d7176ef64959e094c493df8f49e7e8e8f62fe1e1" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-macos-b9c6227.pom">
<sha256 value="143a9bfc539101d8293b7d151d6a952135fa5ad76d752639d2ed72fb9c9c494d" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-windows" version="6d1fd95">
<artifact name="tor-binary-windows-6d1fd95.jar">
<sha256 value="8e0dee7429228aa0c9f7a36f40f303a016ed8dfb40fea77382f7076c13fc27f1" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-windows-6d1fd95.pom">
<sha256 value="08dd80bd3c5e6c6b031ea3e28d8819adec875593a8f1fb9101c0f952f8307b80" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-windows" version="787183b147286d783a6392bb9ffcd8ba920d6fff">
<artifact name="tor-binary-windows-787183b147286d783a6392bb9ffcd8ba920d6fff.jar">
<sha256 value="eebd616315cb7263f07837d5a95c96fdcd627f7fcbfc69e9ca7b840495895197" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-windows-787183b147286d783a6392bb9ffcd8ba920d6fff.pom">
<sha256 value="fa1cc1b84e4705b9102f269a3ec2602e00ed8dae035d99f60a70194551dc8e08" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.bisq-network.tor-binary" name="tor-binary-windows" version="b9c6227">
<artifact name="tor-binary-windows-b9c6227.jar">
<sha256 value="28a1031d7610863f774eedbd00b83b06b132781c31077b805033299de3e3a263" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-windows-b9c6227.pom">
<sha256 value="e067cfa37ee54a2f31d05391319e46484366fda4ef0ee28c3483194b02025e8f" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="com.github.johnrengelman" name="shadow" version="8.1.1">
<artifact name="shadow-8.1.1.jar">
<sha256 value="084197555590a53bb21b59508a3330559f536ddb448eafd1ec675f5462036fcf" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
<component group="com.github.mmazi" name="rescu" version="2.0.2">
<artifact name="rescu-2.0.2.jar">
<sha256 value="bbc3a16d19468f76f9a6906453508bff2c33df5caaae349c4e3b796440bb199a" origin="Generated by Gradle"/>
</artifact>
<artifact name="rescu-2.0.2.pom">
<sha256 value="3e979bc1d06e5f92fe961e262a9e5ebd013ccfae9c0abdfe1eca11838df64a05" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="com.github.mmazi" name="rescu" version="2.1.0">
<artifact name="rescu-2.1.0.jar">
<sha256 value="7d4d4498f052019407b200839bff61d1cdb0a34fb78fd31bbb8accae5f650805" origin="Generated by Gradle"/>
</artifact>
<artifact name="rescu-2.1.0.pom">
<sha256 value="6af31b34813f2de4e201e1d33d51e0b497180e4d48f139e17b22302ac5c36b2b" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.github.ravn" name="jsocks" version="567e1cd">
<artifact name="jsocks-567e1cd.jar">
<sha256 value="3c71600af027b2b6d4244e4ad14d98ff2352a379410daebefff5d8cd48d742a4" origin="Generated by Gradle"/>
</artifact>
<artifact name="jsocks-567e1cd.pom">
<sha256 value="10fb4a4eaed3cb98d5f73f09eb182a1c47432031e600a7506e47f58495079c66" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google" name="google" version="5">
<artifact name="google-5.pom">
<sha256 value="e09d345e73ca3fbca7f3e05f30deb74e9d39dd6b79a93fee8c511f23417b6828" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.android" name="annotations" version="4.1.1.4">
<artifact name="annotations-4.1.1.4.jar">
<sha256 value="ba734e1e84c09d615af6a09d33034b4f0442f8772dec120efb376d86a565ae15" origin="Generated by Gradle"/>
</artifact>
<artifact name="annotations-4.1.1.4.pom">
<sha256 value="e4bb54753c36a27a0e5d70154a5034fedd8feac4282295034bfd483d6c7aae78" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api" name="api-common" version="1.5.0">
<artifact name="api-common-1.5.0.jar">
<sha256 value="adb72815b8a1fd33259fffcc082d7d8dee07303be2e8833f454a70230c73bd62" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api" name="gax" version="1.23.0">
<artifact name="gax-1.23.0.jar">
<sha256 value="eec68d6f3df6bc03cdd21af9c4ea1cfbc648d317581c265e674935c4c9ab199f" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api" name="gax-grpc" version="1.23.0">
<artifact name="gax-grpc-1.23.0.jar">
<sha256 value="f768a0e7a9efb0b2e56d661635290ae4c01edcf5a2d7a595568d2488e8f1aef5" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api" name="gax-httpjson" version="0.40.0">
<artifact name="gax-httpjson-0.40.0.jar">
<sha256 value="97351969c1a23bfcb37a563712fd6e836236f815dd5c451bbb7d0db9756e575c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api-client" name="google-api-client" version="1.23.0">
<artifact name="google-api-client-1.23.0.jar">
<sha256 value="357de0017d439c021a6a98d48e380a25a709dc9bc50e4b38c6ab84094e6f2e84" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api-client" name="google-api-client-gson" version="1.23.0">
<artifact name="google-api-client-gson-1.23.0.jar">
<sha256 value="225c1ed01ecf47c04527541b0de9f8dc87d597af44fd23ef16f570c04468f4b3" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api.grpc" name="proto-google-cloud-firestore-v1beta1" version="0.10.0">
<artifact name="proto-google-cloud-firestore-v1beta1-0.10.0.jar">
<sha256 value="39d0a0a3b4da3b525d3fd7b82c2fbd0d14b6aa486bd49a8a5247dea5b048c13c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api.grpc" name="proto-google-common-protos" version="1.12.0">
<artifact name="proto-google-common-protos-1.12.0.jar">
<sha256 value="bd60cd7a423b00fb824c27bdd0293aaf4781be1daba6ed256311103fb4b84108" origin="Generated by Gradle"/>
</artifact>
<artifact name="proto-google-common-protos-1.12.0.pom">
<sha256 value="1562bd44df27231d5eb1641625df72b0fe13e29feeaf55527c85e617decf0e3a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.api.grpc" name="proto-google-common-protos" version="1.9.0">
<artifact name="proto-google-common-protos-1.9.0.jar">
<sha256 value="cd38ead0263187036caadaa84e8730a59ff821773c736f4188c3c1ed1472a3a1" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.api.grpc" name="proto-google-common-protos" version="2.0.1">
<artifact name="proto-google-common-protos-2.0.1.jar">
<sha256 value="5ce71656118618731e34a5d4c61aa3a031be23446dc7de8b5a5e77b66ebcd6ef" origin="Generated by Gradle"/>
</artifact>
<artifact name="proto-google-common-protos-2.0.1.pom">
<sha256 value="8b62bfd85d693ebcffd828232af7424f34fd212c5e28e5ed99b0dc5d2bc7d4f5" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.api.grpc" name="proto-google-iam-v1" version="0.10.0">
<artifact name="proto-google-iam-v1-0.10.0.jar">
<sha256 value="9a0dbd79f0cf52a2b07f5dc4c151d1bfe4364b48e3f6573510dfce841bfa3b87" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.apis" name="google-api-services-storage" version="v1-rev114-1.23.0">
<artifact name="google-api-services-storage-v1-rev114-1.23.0.jar">
<sha256 value="b14873c309bb45d4b4e35da405f0296b1af48f164b809bebaa603354e618daa7" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.auth" name="google-auth-library-credentials" version="0.17.1">
<artifact name="google-auth-library-credentials-0.17.1.jar">
<sha256 value="aaeea9333fff9b763715bca0174ec76c4f9551b5731c89a95f263cdc82b4b56e" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.auth" name="google-auth-library-credentials" version="0.22.2">
<artifact name="google-auth-library-credentials-0.22.2.jar">
<sha256 value="e42c2cbe642744f55bd2a081e6f60f126e691129e7148daec3af79deab4ac65a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.auth" name="google-auth-library-oauth2-http" version="0.9.0">
<artifact name="google-auth-library-oauth2-http-0.9.0.jar">
<sha256 value="e55d9722102cc1245c8c43d69acd49d3c9bbfcc1bcf722e971425506b970097e" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.auto.value" name="auto-value" version="1.4">
<artifact name="auto-value-1.4.jar">
<sha256 value="64eb1e909354ca11a03661bd6d2d00fc4669a329b26bbd7f2f4fe08fef8699f9" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.cloud" name="google-cloud-core" version="1.27.0">
<artifact name="google-cloud-core-1.27.0.jar">
<sha256 value="989839b68b15e4a63b9554fa4fce29bd1151777b676c7cedfc2a22e3cf1bf7be" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.cloud" name="google-cloud-core-grpc" version="1.27.0">
<artifact name="google-cloud-core-grpc-1.27.0.jar">
<sha256 value="723b4649d08309467f08bbf9f583fc4a87f5c06c132032bad0dab05597f4c2ab" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.cloud" name="google-cloud-core-http" version="1.27.0">
<artifact name="google-cloud-core-http-1.27.0.jar">
<sha256 value="6b9663361a9168b92b2388f8215a30cd34f649bc942d7be79a734ac4ed17ac98" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.cloud" name="google-cloud-firestore" version="0.45.0-beta">
<artifact name="google-cloud-firestore-0.45.0-beta.jar">
<sha256 value="3164f3c1f8e4ef7510ff2594c637e6cd6f2f299952a773d13049660a0ee18587" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.cloud" name="google-cloud-storage" version="1.27.0">
<artifact name="google-cloud-storage-1.27.0.jar">
<sha256 value="b3a739d4b6563ffa0d00629689f8cd11f838ec7b11bf2f69f492f0c5e3ed80c6" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.code.findbugs" name="jsr305" version="3.0.2">
<artifact name="jsr305-3.0.2.jar">
<sha256 value="766ad2a0783f2687962c8ad74ceecc38a28b9f72a2d085ee438b7813e928d0c7" origin="Generated by Gradle"/>
</artifact>
<artifact name="jsr305-3.0.2.pom">
<sha256 value="19889dbdf1b254b2601a5ee645b8147a974644882297684c798afe5d63d78dfe" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.code.gson" name="gson" version="2.8.0">
<artifact name="gson-2.8.0.jar">
<sha256 value="c6221763bd79c4f1c3dc7f750b5f29a0bb38b367b81314c4f71896e340c40825" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.code.gson" name="gson" version="2.8.2">
<artifact name="gson-2.8.2.jar">
<sha256 value="b7134929f7cc7c04021ec1cc27ef63ab907e410cf0588e397b8851181eb91092" origin="Generated by Gradle"/>
</artifact>
<artifact name="gson-2.8.2.pom">
<sha256 value="91b9f17a54e6c340c8d3ea4b359401170706eb26a82d51909abe6ba80081aed8" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.code.gson" name="gson" version="2.8.5">
<artifact name="gson-2.8.5.jar">
<sha256 value="233a0149fc365c9f6edbd683cfe266b19bdc773be98eabdaf6b3c924b48e7d81" origin="Generated by Gradle"/>
</artifact>
<artifact name="gson-2.8.5.pom">
<sha256 value="b8308557a7fccc92d9fe7c8cd0599258b361285d2ecde7689eda98843255a092" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.code.gson" name="gson" version="2.8.6">
<artifact name="gson-2.8.6.jar">
<sha256 value="c8fb4839054d280b3033f800d1f5a97de2f028eb8ba2eb458ad287e536f3f25f" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.code.gson" name="gson-parent" version="2.8.2">
<artifact name="gson-parent-2.8.2.pom">
<sha256 value="cf5c43860b53ba5a95c19bc6525cc43d3488a6fe3df2f649c0099a613a0640e3" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.code.gson" name="gson-parent" version="2.8.5">
<artifact name="gson-parent-2.8.5.pom">
<sha256 value="8f1fec72b91a71ea39ec39f5f778c4d1124b6b097c6d55b3a50b554a52237b27" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="com.google.errorprone" name="error_prone_annotations" version="2.11.0">
<artifact name="error_prone_annotations-2.11.0.jar">
<sha256 value="721cb91842b46fa056847d104d5225c8b8e1e8b62263b993051e1e5a0137b7ec" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.errorprone" name="error_prone_annotations" version="2.2.0">
<artifact name="error_prone_annotations-2.2.0.jar">
<sha256 value="6ebd22ca1b9d8ec06d41de8d64e0596981d9607b42035f9ed374f9de271a481a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.errorprone" name="error_prone_annotations" version="2.3.4">
<artifact name="error_prone_annotations-2.3.4.jar">
<sha256 value="baf7d6ea97ce606c53e11b6854ba5f2ce7ef5c24dddf0afa18d1260bd25b002c" origin="Generated by Gradle"/>
</artifact>
<artifact name="error_prone_annotations-2.3.4.pom">
<sha256 value="1326738a4b4f7ccacf607b866a11fb85193ef60f6a59461187ce7265f9be5bed" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.errorprone" name="error_prone_annotations" version="2.5.1">
<artifact name="error_prone_annotations-2.5.1.jar">
<sha256 value="ff80626baaf12a09342befd4e84cba9d50662f5fcd7f7a9b3490a6b7cf87e66c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.errorprone" name="error_prone_annotations" version="2.9.0">
<artifact name="error_prone_annotations-2.9.0.jar">
<sha256 value="f947bdc33ae27a6b4aa44799e6c21e1944797bd0010ba43eb82d11446e163694" origin="Generated by Gradle"/>
</artifact>
<artifact name="error_prone_annotations-2.9.0.pom">
<sha256 value="a48ee055c9f475846e21b87029df8982b9f7b5e93cc2656fca8d1bda471408ce" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.errorprone" name="error_prone_parent" version="2.3.4">
<artifact name="error_prone_parent-2.3.4.pom">
<sha256 value="40495b437a60d2398f0fdfc054b89d9c394a82347a274a0721c2e950a4302186" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.errorprone" name="error_prone_parent" version="2.9.0">
<artifact name="error_prone_parent-2.9.0.pom">
<sha256 value="520b123d085975b563e34d04400c6263896f858867ce7fc478dd37f491eae3b4" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.firebase" name="firebase-admin" version="6.2.0">
<artifact name="firebase-admin-6.2.0.jar">
<sha256 value="f34f8a6bd8b576a94d80e9743785512b87f2df2495fa3853b850a264dc47924e" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.gradle" name="osdetector-gradle-plugin" version="1.6.0">
<artifact name="osdetector-gradle-plugin-1.6.0.jar">
<sha256 value="e074d3daa0ca0e5a0c6e2c98fcd9da6645ac520c8d091612ae58bdcde65d0585" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="com.google.gradle" name="osdetector-gradle-plugin" version="1.7.3">
<artifact name="osdetector-gradle-plugin-1.7.3.jar">
<sha256 value="6b4692f913a21b1fb603169ee78ba8f3e4ab2af9d762af9ca88b79126c1c0ad1" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.guava" name="failureaccess" version="1.0.1">
<artifact name="failureaccess-1.0.1.jar">
<sha256 value="a171ee4c734dd2da837e4b16be9df4661afab72a41adaf31eb84dfdaf936ca26" origin="Generated by Gradle"/>
</artifact>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
<artifact name="failureaccess-1.0.1.pom">
<sha256 value="e96042ce78fecba0da2be964522947c87b40a291b5fd3cd672a434924103c4b9" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.guava" name="guava" version="18.0">
<artifact name="guava-18.0.jar">
<sha256 value="d664fbfc03d2e5ce9cab2a44fb01f1d0bf9dfebeccc1a473b1f9ea31f79f6f99" origin="Generated by Gradle"/>
</artifact>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.guava" name="guava" version="20.0">
<artifact name="guava-20.0.jar">
<sha256 value="36a666e3b71ae7f0f0dca23654b67e086e6c93d192f60ba5dfd5519db6c288c8" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.guava" name="guava" version="27.0.1-jre">
<artifact name="guava-27.0.1-jre.jar">
<sha256 value="e1c814fd04492a27c38e0317eabeaa1b3e950ec8010239e400fe90ad6c9107b4" origin="Generated by Gradle"/>
</artifact>
</component>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
<component group="com.google.guava" name="guava" version="28.2-jre">
<artifact name="guava-28.2-jre.jar">
<sha256 value="fc3aa363ad87223d1fbea584eee015a862150f6d34c71f24dc74088a635f08ef" origin="Generated by Gradle"/>
</artifact>
<artifact name="guava-28.2-jre.pom">
<sha256 value="c0805261548dc61ca4c982b59bfaad6503e43190f5e5e444e90b2cf6ab72db94" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.guava" name="guava" version="30.1-android">
<artifact name="guava-30.1-android.jar">
<sha256 value="ea0b5a62b707482eee5cf305c8f35ef91cf4ceaff504f011a5c49c41355f5781" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.guava" name="guava" version="30.1.1-jre">
<artifact name="guava-30.1.1-jre.jar">
<sha256 value="44ce229ce26d880bf3afc362bbfcec34d7e6903d195bbb1db9f3b6e0d9834f06" origin="Generated by Gradle"/>
</artifact>
<artifact name="guava-30.1.1-jre.pom">
<sha256 value="6d18c9188ad4b7855fb7fea6f1793754b41fa1747811ae1e3d753d6fcc9dcc59" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="com.google.guava" name="guava" version="31.1-jre">
<artifact name="guava-31.1-jre.jar">
<sha256 value="a42edc9cab792e39fe39bb94f3fca655ed157ff87a8af78e1d6ba5b07c4a00ab" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.guava" name="guava-jdk5" version="17.0">
<artifact name="guava-jdk5-17.0.jar">
<sha256 value="59bf456547b6dda3ced968cb56f7f2d3e14474e2de2960a32c47e31c1e456c61" origin="Generated by Gradle"/>
</artifact>
</component>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
<component group="com.google.guava" name="guava-parent" version="26.0-android">
<artifact name="guava-parent-26.0-android.pom">
<sha256 value="f8698ab46ca996ce889c1afc8ca4f25eb8ac6b034dc898d4583742360016cc04" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.guava" name="guava-parent" version="28.2-jre">
<artifact name="guava-parent-28.2-jre.pom">
<sha256 value="504a6d18eb81ba6d5a255a262bd823f0168c7f47814d4b524f5fa303ea5617c2" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.guava" name="guava-parent" version="30.1.1-jre">
<artifact name="guava-parent-30.1.1-jre.pom">
<sha256 value="0422bd45ca2497bfa18aad2698324965ed70da0907b8a7d459b7ab3b5eed3834" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.guava" name="listenablefuture" version="9999.0-empty-to-avoid-conflict-with-guava">
<artifact name="listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar">
<sha256 value="b372a037d4230aa57fbeffdef30fd6123f9c0c2db85d0aced00c91b974f33f99" origin="Generated by Gradle"/>
</artifact>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
<artifact name="listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.pom">
<sha256 value="18d4b1db26153d4e55079ce1f76bb1fe05cdb862ef9954a88cbcc4ff38b8679b" origin="Generated by Gradle"/>
</artifact>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</component>
<component group="com.google.http-client" name="google-http-client" version="1.23.0">
<artifact name="google-http-client-1.23.0.jar">
<sha256 value="aab53db0ed1601af9e22ee6d2b138669769356ff88602bb336dbc7ee540910ad" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.http-client" name="google-http-client-appengine" version="1.23.0">
<artifact name="google-http-client-appengine-1.23.0.jar">
<sha256 value="8fbaf7dc2983b8c18fc78446da6fde6b7663ac2a24003a9c28dd62ae44196455" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.http-client" name="google-http-client-gson" version="1.23.0">
<artifact name="google-http-client-gson-1.23.0.jar">
<sha256 value="9d9504a6eb37c9b9a5c69efa2b5be77bcfc24fb95d83d1e2cc4737da7536bc03" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.http-client" name="google-http-client-jackson" version="1.23.0">
<artifact name="google-http-client-jackson-1.23.0.jar">
<sha256 value="aec666c6a2841af121dae1410d1663c536ccc81baefc28828e4bc1457ab6ab91" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.http-client" name="google-http-client-jackson2" version="1.23.0">
<artifact name="google-http-client-jackson2-1.23.0.jar">
<sha256 value="2527e9d1eac4822ba94f6fffe4f0b6d6e757e4a33ece5406674f60b7f6494b06" origin="Generated by Gradle"/>
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="com.google.inject" name="guice" version="5.1.0">
<artifact name="guice-5.1.0.jar">
<sha256 value="4130e50bfac48099c860f0d903b91860c81a249c90f38245f8fed58fc817bc26" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.j2objc" name="j2objc-annotations" version="1.1">
<artifact name="j2objc-annotations-1.1.jar">
<sha256 value="2994a7eb78f2710bd3d3bfb639b2c94e219cedac0d4d084d516e78c16dddecf6" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.j2objc" name="j2objc-annotations" version="1.3">
<artifact name="j2objc-annotations-1.3.jar">
<sha256 value="21af30c92267bd6122c0e0b4d20cccb6641a37eaf956c6540ec471d584e64a7b" origin="Generated by Gradle"/>
</artifact>
<artifact name="j2objc-annotations-1.3.pom">
<sha256 value="5faca824ba115bee458730337dfdb2fcea46ba2fd774d4304edbf30fa6a3f055" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.oauth-client" name="google-oauth-client" version="1.23.0">
<artifact name="google-oauth-client-1.23.0.jar">
<sha256 value="48af1eefee0b6e9e131fc8c65a91df96064144c608187e4344eb7e4f8201006a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.protobuf" name="protobuf-bom" version="3.10.0">
<artifact name="protobuf-bom-3.10.0.pom">
<sha256 value="32ff2307dafc658d0b55b2ad841d625aea5606bb9b0316605165cd6980503243" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.protobuf" name="protobuf-bom" version="3.19.1">
<artifact name="protobuf-bom-3.19.1.pom">
<sha256 value="96623d7afc374800cfdc4eb1e49efdb1b17d762fbe9c7de0e46980de14473170" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.protobuf" name="protobuf-gradle-plugin" version="0.8.10">
<artifact name="protobuf-gradle-plugin-0.8.10.jar">
<sha256 value="3287f2efd60a4d3ee8a95ea6d0cf5223507e231e8661c873f84aad5fcd79e1ef" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.protobuf" name="protobuf-gradle-plugin" version="0.8.17">
<artifact name="protobuf-gradle-plugin-0.8.17.jar">
<sha256 value="233eae7e9a5d5f344aacca30bcd2788d348765c0a391eff6d998809a9596d89c" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.protobuf" name="protobuf-java" version="3.10.0">
<artifact name="protobuf-java-3.10.0.jar">
<sha256 value="161d7d61a8cb3970891c299578702fd079646e032329d6c2cabf998d191437c9" origin="Generated by Gradle"/>
</artifact>
<artifact name="protobuf-java-3.10.0.pom">
<sha256 value="b404c1b093ec9dea888e02c8dfe8662759586b94efa4f97061cdfc1bbfa15af0" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.protobuf" name="protobuf-java" version="3.19.1">
<artifact name="protobuf-java-3.19.1.jar">
<sha256 value="24f7d0d91797ed230a6d3da93cd80590a4c3aa9a27249f6025b5c6da078edde7" origin="Generated by Gradle"/>
</artifact>
<artifact name="protobuf-java-3.19.1.pom">
<sha256 value="5de4666f7f6b003d982f48f18c8e22facef6707365a74e20df7cbad98c931dd7" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.protobuf" name="protobuf-java" version="3.5.1">
<artifact name="protobuf-java-3.5.1.jar">
<sha256 value="b5e2d91812d183c9f053ffeebcbcda034d4de6679521940a19064714966c2cd4" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.protobuf" name="protobuf-java-util" version="3.5.1">
<artifact name="protobuf-java-util-3.5.1.jar">
<sha256 value="8bd8a5de6d7e05dce16c8198c8013ebd9c703e10db957fb6dfab0ad24bcd8adc" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.protobuf" name="protobuf-parent" version="3.10.0">
<artifact name="protobuf-parent-3.10.0.pom">
<sha256 value="6dd84a508125fffdefbd583fae12bf166aa902511b570ca54fa9efa45f6dfe80" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.protobuf" name="protobuf-parent" version="3.19.1">
<artifact name="protobuf-parent-3.19.1.pom">
<sha256 value="83d413b2a79d6357d2ca78fd623143424e8f6ecc72cfa83bf2ae2ae258a93a44" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.protobuf" name="protoc" version="3.10.0">
<artifact name="protoc-3.10.0-linux-x86_64.exe">
<sha256 value="eed3ea189a99e3ad4e4209332e7161b255dc8f39bbde4c8e9fc25535f0f6f4f5" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-3.10.0-osx-x86_64.exe">
<sha256 value="a73d5bc8a2a4ab2a541901aa5ce81beacf8a7be5635be06a99c88f5ec10e840f" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-3.10.0-windows-x86_64.exe">
<sha256 value="996fe8523c4d6b70f6e390c9105fbe76023e8fc7aac0ad5e316ec0a48ad9a9b2" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.google.protobuf" name="protoc" version="3.19.1">
<artifact name="protoc-3.19.1-linux-x86_64.exe">
<sha256 value="0b1099f537d44ee862b0c3708f32f1d66cfd76e2e2c1437f0c57a98476c20605" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-3.19.1-osx-aarch_64.exe">
<sha256 value="3431ad66f3bb24cd5196e92a561b0e03bf2906c894bc94d131daaa637094abac" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-3.19.1-osx-x86_64.exe">
<sha256 value="3431ad66f3bb24cd5196e92a561b0e03bf2906c894bc94d131daaa637094abac" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-3.19.1-windows-x86_64.exe">
<sha256 value="06f65a95ee0fb212c45473e0e65cca824e4634b291fe8dd666068edf51e6ca4c" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-3.19.1.pom">
<sha256 value="71a3da76c0c3b7bedb71c1e65f18f47193cc73ef1f27fc26b0a70715794019b7" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.google.zxing" name="core" version="2.0">
<artifact name="core-2.0.jar">
<sha256 value="11aae8fd974ab25faa8208be50468eb12349cd239e93e7c797377fa13e381729" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.zxing" name="javase" version="2.0">
<artifact name="javase-2.0.jar">
<sha256 value="0ec23e2ec12664ddd6347c8920ad647bb3b9da290f897a88516014b56cc77eb9" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.googlecode.jcsv" name="jcsv" version="1.4.0">
<artifact name="jcsv-1.4.0.jar">
<sha256 value="73ca7d715e90c8d2c2635cc284543b038245a34f70790660ed590e157b8714a2" origin="Generated by Gradle"/>
</artifact>
</component>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
<component group="com.gradle" name="gradle-enterprise-gradle-plugin" version="3.12.4">
<artifact name="gradle-enterprise-gradle-plugin-3.12.4.jar">
<sha256 value="6d4be23b57303f3619bf061f3961022f673a6b74b955098fd04ad2cffc0b7109" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
Upgrade Gradle wrapper to 8.5
2023-12-13 20:59:14 +00:00
<component group="com.gradle" name="gradle-enterprise-gradle-plugin" version="3.15.1">
<artifact name="gradle-enterprise-gradle-plugin-3.15.1.jar">
<sha256 value="a25c057eb8bf6e42e5659636d5fbe66332f5966930f3b2bd64c5dd17e45b9dc6" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.jfoenix" name="jfoenix" version="9.0.10">
<artifact name="jfoenix-9.0.10.jar">
<sha256 value="8060235fec5eb49617ec8d81d379e8c945f6cc722d0645e97190045100de2084" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.natpryce" name="make-it-easy" version="4.0.1">
<artifact name="make-it-easy-4.0.1.jar">
<sha256 value="bf28701b65b88532a8bff65a636d7339d6c5db95b2b502799195a15c24fff45b" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.oracle.database.jdbc" name="ojdbc-bom" version="21.3.0.0">
<artifact name="ojdbc-bom-21.3.0.0.pom">
<sha256 value="fb4907da9d458481960df6d153fcc97701646c31888536b42de723d7fa777fc1" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="com.puppycrawl.tools" name="checkstyle" version="10.8.1">
<artifact name="checkstyle-10.8.1.jar">
<sha256 value="3d49a340e09bfa4877d9d07a3bb05ee7161f334a9acc5c820a8a465873226787" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.querydsl" name="querydsl-bom" version="5.0.0">
<artifact name="querydsl-bom-5.0.0.pom">
<sha256 value="33d88ac02fc8c1bdac129dc118ffda3b17fe96bf5cf83541ddc014a29b627b1b" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.sparkjava" name="spark-core" version="2.5.2">
<artifact name="spark-core-2.5.2.jar">
<sha256 value="76c246771297ebb14196eb2be621a1ab2d5b15d3038cb69f3becff1193e176bc" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="com.sun.activation" name="all" version="1.2.2">
<artifact name="all-1.2.2.pom">
<sha256 value="1973d499cc2c1264aff2d6d052a1c716ae613d018ae1c2f610dd6a4d1c24578e" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="com.turo" name="pushy" version="0.13.2">
<artifact name="pushy-0.13.2.jar">
<sha256 value="6125ccbad18bdaf92b483e076b990bfd25da24bdb5bcb087308a31890a30911b" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="commons-beanutils" name="commons-beanutils" version="1.9.4">
<artifact name="commons-beanutils-1.9.4.jar">
<sha256 value="7d938c81789028045c08c065e94be75fc280527620d5bd62b519d5838532368a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="commons-codec" name="commons-codec" version="1.10">
<artifact name="commons-codec-1.10.jar">
<sha256 value="4241dfa94e711d435f29a4604a3e2de5c4aa3c165e23bd066be6fc1fc4309569" origin="Generated by Gradle"/>
</artifact>
<artifact name="commons-codec-1.10.pom">
<sha256 value="bdb8db7012d112a6e3ea8fdb7c510b300d99eff0819d27dddba9c43397ea4cfb" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="commons-codec" name="commons-codec" version="1.11">
<artifact name="commons-codec-1.11.jar">
<sha256 value="e599d5318e97aa48f42136a2927e6dfa4e8881dff0e6c8e3109ddbbff51d7b7d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="commons-codec" name="commons-codec" version="1.13">
<artifact name="commons-codec-1.13.jar">
<sha256 value="61f7a3079e92b9fdd605238d0295af5fd11ac411a0a0af48deace1f6c5ffa072" origin="Generated by Gradle"/>
</artifact>
<artifact name="commons-codec-1.13.pom">
<sha256 value="c2e2a902d38230cf3031d0b434d5de2614fa0ff26d384b6d282aab56c7d3fc69" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="commons-codec" name="commons-codec" version="1.15">
<artifact name="commons-codec-1.15.jar">
<sha256 value="b3e9f6d63a790109bf0d056611fbed1cf69055826defeb9894a71369d246ed63" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="commons-collections" name="commons-collections" version="3.2.2">
<artifact name="commons-collections-3.2.2.jar">
<sha256 value="eeeae917917144a68a741d4c0dff66aa5c5c5fd85593ff217bced3fc8ca783b8" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="commons-io" name="commons-io" version="2.11.0">
<artifact name="commons-io-2.11.0.jar">
<sha256 value="961b2f6d87dbacc5d54abf45ab7a6e2495f89b75598962d8c723cea9bc210908" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="commons-io" name="commons-io" version="2.6">
<artifact name="commons-io-2.6.jar">
<sha256 value="f877d304660ac2a142f3865badfc971dec7ed73c747c7f8d5d2f5139ca736513" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="commons-lang" name="commons-lang" version="2.6">
<artifact name="commons-lang-2.6.jar">
<sha256 value="50f11b09f877c294d56f24463f47d28f929cf5044f648661c0f0cfbae9a2f49c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="commons-logging" name="commons-logging" version="1.2">
<artifact name="commons-logging-1.2.jar">
<sha256 value="daddea1ea0be0f56978ab3006b8ac92834afeefbd9b7e4e6316fca57df0fa636" origin="Generated by Gradle"/>
</artifact>
<artifact name="commons-logging-1.2.pom">
<sha256 value="c91ab5aa570d86f6fd07cc158ec6bc2c50080402972ee9179fe24100739fbb20" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="de.jensd" name="fontawesomefx" version="8.0.0">
<artifact name="fontawesomefx-8.0.0.jar">
<sha256 value="73bacc991a0a6f5cf0f911767c8db161e0949dbca61e8371eb4342e3da96887b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="de.jensd" name="fontawesomefx-commons" version="9.1.2">
<artifact name="fontawesomefx-commons-9.1.2.jar">
<sha256 value="5539bb3335ecb822dbf928546f57766eeb9f1516cc1417a064b5709629612149" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="de.jensd" name="fontawesomefx-materialdesignfont" version="2.0.26-9.1.2">
<artifact name="fontawesomefx-materialdesignfont-2.0.26-9.1.2.jar">
<sha256 value="dbad8dfdd1c85e298d5bbae25b2399aec9e85064db57b2427d10f3815aa98752" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="eu.neilalexander" name="jnacl" version="1.0.0">
<artifact name="jnacl-1.0.0.jar">
<sha256 value="4accc9d2a56a6dd5198ec5e1c5c05a091da563bccd346fd6578edc083152beaa" origin="Generated by Gradle"/>
</artifact>
<artifact name="jnacl-1.0.0.pom">
<sha256 value="76b4a485a8c4c4f35d6d1c6af89c15cd8c3ad4f65671bd191ab822fefeba4147" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="info.picocli" name="picocli" version="4.7.1">
<artifact name="picocli-4.7.1.jar">
<sha256 value="0e7191fbe324fb9df8d2d207c07b666b8dc25bbbe26f53a4c52e2fece624a976" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.dropwizard.metrics" name="metrics-bom" version="4.2.7">
<artifact name="metrics-bom-4.2.7.pom">
<sha256 value="42aff109c893a58b7e9d5c8d355983c45af1a1b25b4a9731c73d412817d734a5" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.dropwizard.metrics" name="metrics-parent" version="4.2.7">
<artifact name="metrics-parent-4.2.7.pom">
<sha256 value="a87b3685a64b9a4154b48d976eb9607e0f40ae11f4498e570287ab7a96164b90" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.github.microutils" name="kotlin-logging" version="1.5.4">
<artifact name="kotlin-logging-1.5.4.jar">
<sha256 value="4992504fd3c6ecdf9ed10874b9508e758bb908af9e9d7af19a61e9afb6b7e27a" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-logging-1.5.4.pom">
<sha256 value="4728eddd64e6ae3e1f205a775c6a327b24bd990b86d528584a17450a8b5f00d6" origin="Generated by Gradle"/>
</artifact>
</component>
update monero-java to v0.8.8
2023-11-12 11:09:19 +00:00
<component group="io.github.monero-ecosystem" name="monero-java" version="0.8.8">
<artifact name="monero-java-0.8.8.jar">
<sha256 value="41be77087c30e76133031b66eb18d35c856047f91b3585e5d8a00badb3089bcb" origin="Generated by Gradle"/>
update to monero-project v0.18.0.0, monero-java v0.7.2
2022-08-06 22:36:09 +00:00
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="io.github.resilience4j" name="resilience4j-all" version="1.7.0">
<artifact name="resilience4j-all-1.7.0.jar">
<sha256 value="46c17f491886c0152d957cd04b00b871f39df09d2bd01067d650e2bc89451b04" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-all-1.7.0.pom">
<sha256 value="9576a2030f8c372a53dbecc1c682e72c4bb4e14a08a35ea57f7bd1a002ee479b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.resilience4j" name="resilience4j-bulkhead" version="1.7.0">
<artifact name="resilience4j-bulkhead-1.7.0.jar">
<sha256 value="639ffb64df8b243a8f1b26939ca03574d7cb53a76c9cfded48ee0cbdee36ef5b" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-bulkhead-1.7.0.pom">
<sha256 value="a7e4f4e142900b830e25b5b0320dba3b5b728d4afbb2ca7c4c6e01b40f7b696b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.resilience4j" name="resilience4j-cache" version="1.7.0">
<artifact name="resilience4j-cache-1.7.0.jar">
<sha256 value="be58ee7affa55db55eb6bd586dda3d427d0339641580aa85f94c1f5706d2415f" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-cache-1.7.0.pom">
<sha256 value="f9186267c4fd2a1e62c9000674db223b8ff0830db884d6972eaf621708c94d88" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.resilience4j" name="resilience4j-circuitbreaker" version="1.7.0">
<artifact name="resilience4j-circuitbreaker-1.7.0.jar">
<sha256 value="4d58d051ecef3a7a6d2aedfe652a152b78b2051f9bf61d12e123efd95eefb4ed" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-circuitbreaker-1.7.0.pom">
<sha256 value="e36475dbce3f45d41f61a49afba61bfd8f4a9f179c5e5470d2e9c13c3152b3cd" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.resilience4j" name="resilience4j-core" version="1.7.0">
<artifact name="resilience4j-core-1.7.0.jar">
<sha256 value="90b3e6a9855fffcfd6fbca5a4ff2ae4cabcc3b7c763aefadf94556a234168be3" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-core-1.7.0.pom">
<sha256 value="e6aed8dd799954402e189ca16d5ebba04c0c29a6e2d5e050d3e61f4ecd0d80ac" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.resilience4j" name="resilience4j-ratelimiter" version="1.7.0">
<artifact name="resilience4j-ratelimiter-1.7.0.jar">
<sha256 value="4829d28fd83a6bdd07131dde551544536e15d1b783cffeceec4b6032c6e78123" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-ratelimiter-1.7.0.pom">
<sha256 value="99e72a9a620f6b7150d9a922c70b089ef1d150f52794339901279831b954390f" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.resilience4j" name="resilience4j-retry" version="1.7.0">
<artifact name="resilience4j-retry-1.7.0.jar">
<sha256 value="bce67fdf8c73b4f436e77918c597fbea7173cbe4ad8b51f02df424992217e2d1" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-retry-1.7.0.pom">
<sha256 value="d725333796ef9686504f204d69772c654ae8b227c3a51b97dc5690652a9d24b4" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.resilience4j" name="resilience4j-timelimiter" version="1.7.0">
<artifact name="resilience4j-timelimiter-1.7.0.jar">
<sha256 value="6a06f4cd637dbc89f557ad1b4746d629ec01c6230ef439417df2403397eb2bd6" origin="Generated by Gradle"/>
</artifact>
<artifact name="resilience4j-timelimiter-1.7.0.pom">
<sha256 value="c92e2ca40a3f2474d61e56831aeb379cf8ae3dddeea61b4a828cee2d99f71f38" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-api" version="1.25.0">
<artifact name="grpc-api-1.25.0.jar">
<sha256 value="a269094009588213ab5386a6fb92426b8056a130b2653d3b4e59e971f2f1ef08" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-api-1.25.0.pom">
<sha256 value="8aa2955fdb4a893dacd88a4de00812e841fd5f9b1c184263b7e60aa53d59b568" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-api" version="1.42.1">
<artifact name="grpc-api-1.42.1.jar">
<sha256 value="e2c9cf24bf260af99c9a1ee1e587b0ebd45b14c3bfb655050401a02f67c9436c" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-api-1.42.1.pom">
<sha256 value="e371abe8a43de8416afa1a970466d833d1974f86ed620a5f548ab5aac4610188" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-auth" version="1.25.0">
<artifact name="grpc-auth-1.25.0.jar">
<sha256 value="782ae07923d53b56f54326e7b32480b425eb3df71deb5a4a33bbfc6487e706a4" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-auth" version="1.42.1">
<artifact name="grpc-auth-1.42.1.jar">
<sha256 value="fbfeae9b1b8b913f82a8ed5c20d4536a404464bfd385fd8ecd5a7dac9207ce30" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-context" version="1.25.0">
<artifact name="grpc-context-1.25.0.jar">
<sha256 value="f4c8f878c320f6fb56c1c14692618f6df8253314b556176e32727afbc5921a73" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-context-1.25.0.pom">
<sha256 value="7658b40a601548133a6ca8c93fa88761aa55f13359d179fc688694844d5702a8" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-context" version="1.42.1">
<artifact name="grpc-context-1.42.1.jar">
<sha256 value="8810d6dc294b8c025c152a0093a2c62406ed79778f52ebbb28ab51640c1a4504" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-context-1.42.1.pom">
<sha256 value="f5e039aef6d179366e83a5bd9a1fda10d73c8131ed7232d4c782b1bd7b1ba762" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-core" version="1.10.1">
<artifact name="grpc-core-1.10.1.jar">
<sha256 value="a8327173b619137ea1b32da4cb06bf3728a5e9b6b40c6249b5c33dcc2eb6a572" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.grpc" name="grpc-core" version="1.25.0">
<artifact name="grpc-core-1.25.0.jar">
<sha256 value="d67fa113fd9cc45a02710f9c41dda9c15191448c14e9e96fcc21839a41345d4c" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-core-1.25.0.pom">
<sha256 value="84c3213dd54b7f06b8592ac685c75ff03115cec3ed825c5de14658d7ecab69be" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-core" version="1.42.1">
<artifact name="grpc-core-1.42.1.jar">
<sha256 value="0ae05bd478bbcfbd99840fac07cadbab100f597ceae2f8d122536778a26fed1f" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-core-1.42.1.pom">
<sha256 value="ddcff88dda0a4f9380a09400e435b3c555121e64ea2770966a860b9df66a8d8b" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-netty-shaded" version="1.10.1">
<artifact name="grpc-netty-shaded-1.10.1.jar">
<sha256 value="65558b1f7145ad285acbb57e3fe7129bfd8660104ed4f874223043d615925105" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.grpc" name="grpc-netty-shaded" version="1.25.0">
<artifact name="grpc-netty-shaded-1.25.0.jar">
<sha256 value="9edfd45da473d2efbb5683fc3eaf1857e82d2148033d82dd558a7ac38731ea33" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-netty-shaded-1.25.0.pom">
<sha256 value="26a27dd8a7bb5ce04eae4455fd260c914cd6d9d8a2cad1a804c58563ff5fd01f" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-netty-shaded" version="1.42.1">
<artifact name="grpc-netty-shaded-1.42.1.jar">
<sha256 value="154ff51536c888708afb2d8437df09a8bc5fe2607b01b2ffd2c1980c353ad168" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-netty-shaded-1.42.1.pom">
<sha256 value="c1e9252e1fd85f8d7d5bdb1d5034e88d31105852a1c95e130bf39f969046142d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-protobuf" version="1.10.1">
<artifact name="grpc-protobuf-1.10.1.jar">
<sha256 value="3f7365986cb37edd66a5550938650a753de7d54571e3670c3aa414752f436c8b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.grpc" name="grpc-protobuf" version="1.25.0">
<artifact name="grpc-protobuf-1.25.0.jar">
<sha256 value="454dae7e246dac25526ed5b795d97a5dafedd3cc2042cfc810f02051d7d3e3cb" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-protobuf-1.25.0.pom">
<sha256 value="76399ced4a9af69b83a2ca0d5df85d0f94b0401c1f9005b84c6987185216e6f8" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-protobuf" version="1.42.1">
<artifact name="grpc-protobuf-1.42.1.jar">
<sha256 value="272ddd7486c11d4e4b4a534953b9dbf94ee752c5a87f9d390d50d2c14f0d7bac" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-protobuf-1.42.1.pom">
<sha256 value="b58bec6b6af035f8cfbe51577035d12d712bc1f6cc7f8cbbe0cfac02a535d0e8" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-protobuf-lite" version="1.10.1">
<artifact name="grpc-protobuf-lite-1.10.1.jar">
<sha256 value="326a4fc6a2adc214f80d45a9b35024ac63e96d9c8d870a43bd48fa6322111027" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.grpc" name="grpc-protobuf-lite" version="1.25.0">
<artifact name="grpc-protobuf-lite-1.25.0.jar">
<sha256 value="9ba9aaa3e6997a04c707793c25e3ec88c6bad86f8d6f6b8b7a1a0c33ea2429d8" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-protobuf-lite-1.25.0.pom">
<sha256 value="ff6b3de50e680ba7a40b39981717f485351513d1de3e299866ff94cfaed51573" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-protobuf-lite" version="1.42.1">
<artifact name="grpc-protobuf-lite-1.42.1.jar">
<sha256 value="bb258c38d98a1de473569c56b66f31f101e528feb5b790215b41117573e6885d" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-protobuf-lite-1.42.1.pom">
<sha256 value="9b8cd86df5193b81d5a749e8f247cd7b83901014a2d4d4a78c8e13449b82e915" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="grpc-stub" version="1.10.1">
<artifact name="grpc-stub-1.10.1.jar">
<sha256 value="8bcd29c6236d1e0baf65f1bebddf85517e10322ee171c3230b172801e7340b9d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.grpc" name="grpc-stub" version="1.25.0">
<artifact name="grpc-stub-1.25.0.jar">
<sha256 value="1532e291c0e9fd8230a6416c8ebbd902d99c7e2760241ae638ea761aa3dd5f43" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-stub-1.25.0.pom">
<sha256 value="8afcbbed84d3d3f64e902ec5ff08b34f670232ed377307692d1dae0699211567" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="grpc-stub" version="1.42.1">
<artifact name="grpc-stub-1.42.1.jar">
<sha256 value="a3c3f936510476701fff2bd9750bb4346a2c73c4f5446f3a1a897b8ef6a4071f" origin="Generated by Gradle"/>
</artifact>
<artifact name="grpc-stub-1.42.1.pom">
<sha256 value="b8ba8a78520802dc168285d6bf4c85c6558e095eca853713fdbcbc4453875151" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.grpc" name="protoc-gen-grpc-java" version="1.25.0">
<artifact name="protoc-gen-grpc-java-1.25.0-linux-x86_64.exe">
<sha256 value="a712c0af4a0f7261a4880398072da6b482beca2307c2e5c42592d96841ca0ec2" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-gen-grpc-java-1.25.0-osx-x86_64.exe">
<sha256 value="83cc359bce8a615571c6fafc2979a143364b77a53f5b89a194aa8609c0c0c9fa" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-gen-grpc-java-1.25.0-windows-x86_64.exe">
<sha256 value="3186347362277c18082fac6de2525ca8311becbe29e95414fe55559b8dd2fbff" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.grpc" name="protoc-gen-grpc-java" version="1.42.1">
<artifact name="protoc-gen-grpc-java-1.42.1-linux-x86_64.exe">
<sha256 value="5596b69eb69ed508bc69307f14340be702bdee2ff0ed33c1cafde02aefc9faaf" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-gen-grpc-java-1.42.1-osx-aarch_64.exe">
<sha256 value="f343841e08c9cbffdda92278f01f4ab9c2afb91b6125047e4c8d0aaf59736764" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-gen-grpc-java-1.42.1-osx-x86_64.exe">
<sha256 value="f343841e08c9cbffdda92278f01f4ab9c2afb91b6125047e4c8d0aaf59736764" origin="Generated by Gradle"/>
</artifact>
<artifact name="protoc-gen-grpc-java-1.42.1-windows-x86_64.exe">
<sha256 value="cf8a24fd65e2e243aed74f79589d9b0194fd1f7a70063fd523cc0baeb44532a9" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.micrometer" name="micrometer-bom" version="1.8.2">
<artifact name="micrometer-bom-1.8.2.pom">
<sha256 value="60a0090fc5d9fe56df37bd5c27cb88d8bb9223bb3acd7ca06d1147213597633f" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-bom" version="4.1.73.Final">
<artifact name="netty-bom-4.1.73.Final.pom">
<sha256 value="cdead0f5dd8f5e4304de34cbb5c80d393a6a4ecc1dfb6f25aea9691686ca5bd6" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.netty" name="netty-buffer" version="4.1.25.Final">
<artifact name="netty-buffer-4.1.25.Final.jar">
<sha256 value="6adf1adb0a89b44c870b4773996679e6736f3b8f40cedb41e8c3e77e75d3619a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-codec" version="4.1.25.Final">
<artifact name="netty-codec-4.1.25.Final.jar">
<sha256 value="c9c4bf830cb3284028317cb2752f7de54ecddab0142fc7c09cc3ddee0c6c100a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-codec-dns" version="4.1.25.Final">
<artifact name="netty-codec-dns-4.1.25.Final.jar">
<sha256 value="6c41675e1dbaccfdef9295078917381ea5efd607d4ef92145f632b514de79a44" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-codec-http" version="4.1.25.Final">
<artifact name="netty-codec-http-4.1.25.Final.jar">
<sha256 value="77fc6fa42dffe37fac5097d6bc5c546de941ed02972806ffd8d80efb3151d32d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-codec-http2" version="4.1.25.Final">
<artifact name="netty-codec-http2-4.1.25.Final.jar">
<sha256 value="54f4f0012e9404cac014e63b85a72dd4ada89ea208d46969fe5c2b757f55ff40" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-codec-socks" version="4.1.25.Final">
<artifact name="netty-codec-socks-4.1.25.Final.jar">
<sha256 value="df75b12f37e00b65357fb41376c9f98bbedd9b7ee60dad0dfef8544ce14f65ea" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-common" version="4.1.25.Final">
<artifact name="netty-common-4.1.25.Final.jar">
<sha256 value="50697918592b03624d9a6ea1847d3a831d988d17bd44df370113c83dfda6095b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-handler" version="4.1.25.Final">
<artifact name="netty-handler-4.1.25.Final.jar">
<sha256 value="98c45605619a571a75ce82ea49e7c54b2bb2eb5d4ddc3e327ae4559b82b8556a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-handler-proxy" version="4.1.25.Final">
<artifact name="netty-handler-proxy-4.1.25.Final.jar">
<sha256 value="60952dc844c5d247fffafa0d78b05ca575cd6bf3ca753a132adb097c548da7d8" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-resolver" version="4.1.25.Final">
<artifact name="netty-resolver-4.1.25.Final.jar">
<sha256 value="85ea31999ad2cdbaa2f251caf2660a8ef0d9f274b0d86771077e7fd69c02b257" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-resolver-dns" version="4.1.25.Final">
<artifact name="netty-resolver-dns-4.1.25.Final.jar">
<sha256 value="e2bb6ab70f3d3872e55e3127449fa6a2ee8c1a1b9a85b01ac9749fe1f6a0cfd8" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.netty" name="netty-transport" version="4.1.25.Final">
<artifact name="netty-transport-4.1.25.Final.jar">
<sha256 value="278b12a6f2c479124ff44c299c67d50443636ffed6399ae67d71473736cec58d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.opencensus" name="opencensus-api" version="0.11.1">
<artifact name="opencensus-api-0.11.1.jar">
<sha256 value="f0a396d41903e62c1e660f4323fa5d319faae6b6d8fdbaae1e8f9c2ecb286ade" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.opencensus" name="opencensus-api" version="0.21.0">
<artifact name="opencensus-api-0.21.0.jar">
<sha256 value="8e2cb0f6391d8eb0a1bcd01e7748883f0033b1941754f4ed3f19d2c3e4276fc8" origin="Generated by Gradle"/>
</artifact>
<artifact name="opencensus-api-0.21.0.pom">
<sha256 value="e2f1e8cdb498220315cf0fcdd89f1c0abf3b2bccf9a4ec1f5e59ccbe7848439b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.opencensus" name="opencensus-contrib-grpc-metrics" version="0.11.0">
<artifact name="opencensus-contrib-grpc-metrics-0.11.0.jar">
<sha256 value="21c37058d708ff7aed46cc7e0f226d6816190376b086574eafab2c5fa05724fe" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.opencensus" name="opencensus-contrib-grpc-metrics" version="0.21.0">
<artifact name="opencensus-contrib-grpc-metrics-0.21.0.jar">
<sha256 value="29fc79401082301542cab89d7054d2f0825f184492654c950020553ef4ff0ef8" origin="Generated by Gradle"/>
</artifact>
<artifact name="opencensus-contrib-grpc-metrics-0.21.0.pom">
<sha256 value="908885a1e63cd6ee8c5d281404d41ed3d5bcb1a642e1c0a3ab285d378ef0758e" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.opencensus" name="opencensus-contrib-http-util" version="0.11.1">
<artifact name="opencensus-contrib-http-util-0.11.1.jar">
<sha256 value="3d2953b189b70cc37eb7ee9d23cede6e7fc1af0291593b9cc5eace180d7bf6df" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.perfmark" name="perfmark-api" version="0.19.0">
<artifact name="perfmark-api-0.19.0.jar">
<sha256 value="b734ba2149712409a44eabdb799f64768578fee0defe1418bb108fe32ea43e1a" origin="Generated by Gradle"/>
</artifact>
<artifact name="perfmark-api-0.19.0.pom">
<sha256 value="e73b2e78a5d4a8a6fd50dfb7241586c385165115296297112954bf44e81e646c" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="io.perfmark" name="perfmark-api" version="0.23.0">
<artifact name="perfmark-api-0.23.0.jar">
<sha256 value="c705b5c10c18ff3032b9e81742bc2f6b0e5607f6a6dfc0c8ad0cff75d4913042" origin="Generated by Gradle"/>
</artifact>
<artifact name="perfmark-api-0.23.0.pom">
<sha256 value="5e3b8e04061598bcf4ad48a4b44659805656d6b5282a6853d802f1c9cb70e749" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.projectreactor" name="reactor-bom" version="2020.0.15">
<artifact name="reactor-bom-2020.0.15.pom">
<sha256 value="92c5282267379c5bfb4d91f5019d0ee4c07cb4477f15b67c5de86bd92bb14f2c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.prometheus" name="parent" version="0.12.0">
<artifact name="parent-0.12.0.pom">
<sha256 value="5d0918a46f1551a32c73fc2b0f741340d087f583f98d974b040fbf63e96a78ed" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.prometheus" name="simpleclient_bom" version="0.12.0">
<artifact name="simpleclient_bom-0.12.0.pom">
<sha256 value="30b7269eec7b27cc0643628d3a8da3061b9509d9dbca82f145671b681489a2c2" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.r2dbc" name="r2dbc-bom" version="Arabba-SR12">
<artifact name="r2dbc-bom-Arabba-SR12.pom">
<sha256 value="7af647d127aae14a8f09afb03928f19f11b8ba151e8663df34d350d109ea791d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.rsocket" name="rsocket-bom" version="1.1.1">
<artifact name="rsocket-bom-1.1.1.pom">
<sha256 value="393e745d222f86885a0456bba71ab25297dbeab625df286199d20b6a7daa99dd" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.spring.gradle" name="dependency-management-plugin" version="1.0.11.RELEASE">
<artifact name="dependency-management-plugin-1.0.11.RELEASE.jar">
<sha256 value="39ab7c3aa351b700dc8a61c4aa66dc34239f0b7ed62adc66c7ce9e4072d6ac88" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="io.spring.gradle" name="dependency-management-plugin" version="1.0.4.RELEASE">
<artifact name="dependency-management-plugin-1.0.4.RELEASE.jar">
<sha256 value="37e2b4345ee0b0078d39c24424ab952672d37994ba86135d44c2e76279864f5a" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="io.vavr" name="vavr" version="0.10.2">
<artifact name="vavr-0.10.2.jar">
<sha256 value="1b2ae46cf352627e05b39ac1f1d3bda7b285a8f643cdc7472aea4aa279492e54" origin="Generated by Gradle"/>
</artifact>
<artifact name="vavr-0.10.2.pom">
<sha256 value="f85e2ae607e7b23824c0a08b007a059afd61cfac9f6afc87d7baf7de1a0d4cca" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.vavr" name="vavr-match" version="0.10.2">
<artifact name="vavr-match-0.10.2.jar">
<sha256 value="5d7a9515b05e3291194e04e641acf74a9a544c1caa1e2c24f59a1424c6ec8288" origin="Generated by Gradle"/>
</artifact>
<artifact name="vavr-match-0.10.2.pom">
<sha256 value="4b0f8c0be98698b9187be651b55130967dd7e8dd356cff6c6edfd84f3e63e773" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.vavr" name="vavr-parent" version="0.10.2">
<artifact name="vavr-parent-0.10.2.pom">
<sha256 value="91359b2cba15324405169d1e2d1ef4b2d016e394d6eae58677c4f0f87f33cb87" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="jakarta.activation" name="jakarta.activation-api" version="1.2.1">
<artifact name="jakarta.activation-api-1.2.1.jar">
<sha256 value="8b0a0f52fa8b05c5431921a063ed866efaa41dadf2e3a7ee3e1961f2b0d9645b" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="jakarta.activation" name="jakarta.activation-api" version="1.2.2">
<artifact name="jakarta.activation-api-1.2.2.jar">
<sha256 value="a187a939103aef5849a7af84bd7e27be2d120c410af291437375ffe061f4f09d" origin="Generated by Gradle"/>
</artifact>
<artifact name="jakarta.activation-api-1.2.2.pom">
<sha256 value="5e50fe938068471f504a7efc4071823425b520eabc6f80c72d935ebd54683091" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="jakarta.annotation" name="ca-parent" version="1.3.5">
<artifact name="ca-parent-1.3.5.pom">
<sha256 value="bdbb049465f366edb5a4adbff293a841c9b75b238519e76f86fe4f7bfb9d7e2d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="jakarta.annotation" name="jakarta.annotation-api" version="1.3.5">
<artifact name="jakarta.annotation-api-1.3.5.jar">
<sha256 value="85fb03fc054cdf4efca8efd9b6712bbb418e1ab98241c4539c8585bbc23e1b8a" origin="Generated by Gradle"/>
</artifact>
<artifact name="jakarta.annotation-api-1.3.5.pom">
<sha256 value="ba6874767f5415c5e0f644fab80e1bad5feab6d18150f22638067681866feaaf" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="jakarta.ws.rs" name="jakarta.ws.rs-api" version="2.1.5">
<artifact name="jakarta.ws.rs-api-2.1.5.jar">
<sha256 value="3587738aaf6d5e4f1e3f01cc249cb061badf7490f7e647b2ae26d0a7efa6e173" origin="Generated by Gradle"/>
</artifact>
<artifact name="jakarta.ws.rs-api-2.1.5.pom">
<sha256 value="23987ad51189efe6997c9e293b88385cb5cf0e7ad4e54ce24bb0ceb173dda3d4" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="jakarta.ws.rs" name="jakarta.ws.rs-api" version="2.1.6">
<artifact name="jakarta.ws.rs-api-2.1.6.jar">
<sha256 value="4cea299c846c8a6e6470cbfc2f7c391bc29b9caa2f9264ac1064ba91691f4adf" origin="Generated by Gradle"/>
</artifact>
<artifact name="jakarta.ws.rs-api-2.1.6.pom">
<sha256 value="291c18a6dcc54766397774a5c12a2bc9a2f337f4aed62d3f9fbf6c06483b1f36" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="jakarta.xml.bind" name="jakarta.xml.bind-api" version="2.3.2">
<artifact name="jakarta.xml.bind-api-2.3.2.jar">
<sha256 value="69156304079bdeed9fc0ae3b39389f19b3cc4ba4443bc80508995394ead742ea" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="jakarta.xml.bind" name="jakarta.xml.bind-api" version="2.3.3">
<artifact name="jakarta.xml.bind-api-2.3.3.jar">
<sha256 value="c04539f472e9a6dd0c7685ea82d677282269ab8e7baca2e14500e381e0c6cec5" origin="Generated by Gradle"/>
</artifact>
<artifact name="jakarta.xml.bind-api-2.3.3.pom">
<sha256 value="7fe2ca5dce4b14a646bbf921d13ca42caf2a2c0654da155c7563865c989396fd" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="jakarta.xml.bind" name="jakarta.xml.bind-api-parent" version="2.3.3">
<artifact name="jakarta.xml.bind-api-parent-2.3.3.pom">
<sha256 value="280da531760166d4412368d0dd899ef4aebfd0a7d82bf233502e29856806ada9" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="javax.annotation" name="javax.annotation-api" version="1.2">
<artifact name="javax.annotation-api-1.2.jar">
<sha256 value="5909b396ca3a2be10d0eea32c74ef78d816e1b4ead21de1d78de1f890d033e04" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="javax.annotation" name="javax.annotation-api" version="1.3.2">
<artifact name="javax.annotation-api-1.3.2.jar">
<sha256 value="e04ba5195bcd555dc95650f7cc614d151e4bcd52d29a10b8aa2197f3ab89ab9b" origin="Generated by Gradle"/>
</artifact>
<artifact name="javax.annotation-api-1.3.2.pom">
<sha256 value="46a4a251ca406e78e4853d7a2bae83282844a4992851439ee9a1f23716f06b97" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="javax.cache" name="cache-api" version="1.0.0">
<artifact name="cache-api-1.0.0.jar">
<sha256 value="d2836213144722e2eb1d7461f6e2ea3349d6fbbf9cd5f345c7133bc29bd39ca1" origin="Generated by Gradle"/>
</artifact>
<artifact name="cache-api-1.0.0.pom">
<sha256 value="424dd1d4e7e92bffb4bb9f18acf7f53835d218fb9788336b5fdc69cff5c675ef" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="javax.cache" name="cache-api" version="1.1.1">
<artifact name="cache-api-1.1.1.jar">
<sha256 value="9f34e007edfa82a7b2a2e1b969477dcf5099ce7f4f926fb54ce7e27c4a0cd54b" origin="Generated by Gradle"/>
</artifact>
<artifact name="cache-api-1.1.1.pom">
<sha256 value="832a04c9f02f1e427f1e433da63b6f74d40a2902a3c7871e1a81c3cc10021a13" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="javax.inject" name="javax.inject" version="1">
<artifact name="javax.inject-1.jar">
<sha256 value="91c77044a50c481636c32d916fd89c9118a72195390452c81065080f957de7ff" origin="Generated by Gradle"/>
</artifact>
<artifact name="javax.inject-1.pom">
<sha256 value="943e12b100627804638fa285805a0ab788a680266531e650921ebfe4621a8bfa" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="javax.servlet" name="javax.servlet-api" version="3.1.0">
<artifact name="javax.servlet-api-3.1.0.jar">
<sha256 value="af456b2dd41c4e82cf54f3e743bc678973d9fe35bd4d3071fa05c7e5333b8482" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="javax.validation" name="validation-api" version="1.1.0.Final">
<artifact name="validation-api-1.1.0.Final.jar">
<sha256 value="f39d7ba7253e35f5ac48081ec1bc28c5df9b32ac4b7db20853e5a8e76bf7b0ed" origin="Generated by Gradle"/>
</artifact>
<artifact name="validation-api-1.1.0.Final.pom">
<sha256 value="b8634911e6cbe6c14b30bd06e3837d7e6928fc7e1c96278dec61708b6aaee21c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="javax.ws.rs" name="javax.ws.rs-api" version="2.1">
<artifact name="javax.ws.rs-api-2.1.jar">
<sha256 value="1a4295889416c6972addcd425dfeeee6e6ede110e8b2dc8b49044e9b400ad5db" origin="Generated by Gradle"/>
</artifact>
<artifact name="javax.ws.rs-api-2.1.pom">
<sha256 value="d6519b900a0e3b699068ddbdd06ab875a55cdae73ccdb292ae67f8af81eed5e4" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="joda-time" name="joda-time" version="2.9.2">
<artifact name="joda-time-2.9.2.jar">
<sha256 value="0be5c40e8cdce9ec0643d76be99f276db17c45d7616a217fd1b19b7ef73ca7b1" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="junit" name="junit" version="4.12">
<artifact name="junit-4.12.jar">
<sha256 value="59721f0805e223d84b90677887d9ff567dc534d7c502ca903c0c2b17f05c116a" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-4.12.pom">
<sha256 value="90f163f78e3ffb6f1c7ad97de9e7eba4eea25807141b85d6d12be67ca25449c4" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="junit" name="junit" version="4.13.1">
<artifact name="junit-4.13.1.jar">
<sha256 value="c30719db974d6452793fe191b3638a5777005485bae145924044530ffa5f6122" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="kr.motd.maven" name="os-maven-plugin" version="1.7.1">
<artifact name="os-maven-plugin-1.7.1.jar">
<sha256 value="f47aeef86821e52b2b18758978bd045f03d722292e32e747082122c6228952e0" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="net.bytebuddy" name="byte-buddy" version="1.10.15">
<artifact name="byte-buddy-1.10.15.jar">
<sha256 value="79be97529a296fca4a885c4652814a939ae37f1a86a6b13bd29d0725fa4e5711" origin="Generated by Gradle"/>
</artifact>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<artifact name="byte-buddy-1.10.15.pom">
<sha256 value="1cef6524cccce1b5a5fd6b884433cc455d2f20ea0e81340015fdfe58529c6d99" origin="Generated by Gradle"/>
</artifact>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="net.bytebuddy" name="byte-buddy" version="1.11.19">
<artifact name="byte-buddy-1.11.19.jar">
<sha256 value="4cd1038ca54507323bf04742634f618bb1624914df47a8b4a4dcfa797bd6a8d5" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.bytebuddy" name="byte-buddy" version="1.11.22">
<artifact name="byte-buddy-1.11.22.jar">
<sha256 value="d95656262ebce2fbff31b8c041af7170ad8a3cee843cec8f75cdb21f20b4bd96" origin="Generated by Gradle"/>
</artifact>
<artifact name="byte-buddy-1.11.22.pom">
<sha256 value="49e054f69779b67cfee7781253abd073043e7b19ffce1a10cc92c548f5e20110" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="net.bytebuddy" name="byte-buddy" version="1.14.1">
<artifact name="byte-buddy-1.14.1.jar">
<sha256 value="63479f9a0a1b28f98313230d688a46b02bd80d09a700e127482d0bd635b47bad" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="net.bytebuddy" name="byte-buddy-agent" version="1.10.15">
<artifact name="byte-buddy-agent-1.10.15.jar">
<sha256 value="15cecd0ca128d0517d99b5bb8682b4f187c73a68eeff4a1797168322bc0ebc5c" origin="Generated by Gradle"/>
</artifact>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<artifact name="byte-buddy-agent-1.10.15.pom">
<sha256 value="00623295bd3b07abd8e6734950c5b3e4ba0c6545c7439ae1a101adbc40c0748d" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="net.bytebuddy" name="byte-buddy-agent" version="1.11.19">
<artifact name="byte-buddy-agent-1.11.19.jar">
<sha256 value="871ba7021f8c335a14b47012f1bfe2cf8caa7c0b5a57dd1e00ee2b9e1f143fc0" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.bytebuddy" name="byte-buddy-agent" version="1.11.22">
<artifact name="byte-buddy-agent-1.11.22.jar">
<sha256 value="38e8a07d4e2b35de35084cd7aae122e778cf21b528d5fed91f1d974d72be566e" origin="Generated by Gradle"/>
</artifact>
<artifact name="byte-buddy-agent-1.11.22.pom">
<sha256 value="64218a12c36e897b7b62118486c13f9a804568ffc516ca5d9f72dd264dd3a8b3" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="net.bytebuddy" name="byte-buddy-agent" version="1.14.1">
<artifact name="byte-buddy-agent-1.14.1.jar">
<sha256 value="f4809b9d0f00e71be98a61a25b3e14437f53f6821485694011beeb25e9231dde" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="net.bytebuddy" name="byte-buddy-parent" version="1.10.15">
<artifact name="byte-buddy-parent-1.10.15.pom">
<sha256 value="95f928ce833c13bbdfc166e411b408a510012920481a93aa2bf74bee5fd56db1" origin="Generated by Gradle"/>
</artifact>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="net.bytebuddy" name="byte-buddy-parent" version="1.11.22">
<artifact name="byte-buddy-parent-1.11.22.pom">
<sha256 value="adaee3b3e5d63a0f50d1d9aa097103e552e94bed0c58e9e3e3612c720489160d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="net.glxn" name="qrgen" version="1.3">
<artifact name="qrgen-1.3.jar">
<sha256 value="c85d9d8512d91e8ad11fe56259a7825bd50ce0245447e236cf168d1b17591882" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.java" name="jvnet-parent" version="3">
<artifact name="jvnet-parent-3.pom">
<sha256 value="30f5789efa39ddbf96095aada3fc1260c4561faf2f714686717cb2dc5049475a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.java" name="jvnet-parent" version="5">
<artifact name="jvnet-parent-5.pom">
<sha256 value="1af699f8d9ddab67f9a0d202fbd7915eb0362a5a6dfd5ffc54cafa3465c9cb0a" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="net.java.dev.jna" name="jna" version="5.7.0">
<artifact name="jna-5.7.0.jar">
<sha256 value="c34e3e002cca6e197379c105b554255cc0638101ed7a09ef00334dade0013621" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.java.dev.jna" name="jna-platform" version="5.7.0">
<artifact name="jna-platform-5.7.0.jar">
<sha256 value="42e020705692eddbd285e2b72ef0ff468f51a926382569c45f4e9cea4602ad1e" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="net.jcip" name="jcip-annotations" version="1.0">
<artifact name="jcip-annotations-1.0.jar">
<sha256 value="be5805392060c71474bf6c9a67a099471274d30b83eef84bfc4e0889a4f1dcc0" origin="Generated by Gradle"/>
</artifact>
<artifact name="jcip-annotations-1.0.pom">
<sha256 value="5c19e6848cc550a95664fb082304bc5f9fcf7b672faf03af1635f0e93c268177" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.sf.jopt-simple" name="jopt-simple" version="5.0.4">
<artifact name="jopt-simple-5.0.4.jar">
<sha256 value="df26cc58f235f477db07f753ba5a3ab243ebe5789d9f89ecf68dd62ea9a66c28" origin="Generated by Gradle"/>
</artifact>
<artifact name="jopt-simple-5.0.4.pom">
<sha256 value="6a67763b76afcd9c80b95e5c5e24782d18cc1b0e3d9b454ad3f8754c76b76815" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="net.sf.saxon" name="Saxon-HE" version="12.0">
<artifact name="Saxon-HE-12.0.jar">
<sha256 value="ab1eb7d315ee295b9d7901146823a17148a6ca0a0b880153f6592607efebe792" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="oauth.signpost" name="oauth-signpost" version="1.2.1.2">
<artifact name="oauth-signpost-1.2.1.2.pom">
<sha256 value="4ead9d3e3f305a4ed26fd732e6f0df0be2524e2daf2681df1b001fbb8efc9735" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="oauth.signpost" name="signpost-core" version="1.2.1.2">
<artifact name="signpost-core-1.2.1.2.jar">
<sha256 value="a1d69c5346ebf086b0f63c382b4500ceb29304d8fe95157b060aa4cd3861f230" origin="Generated by Gradle"/>
</artifact>
<artifact name="signpost-core-1.2.1.2.pom">
<sha256 value="f3c6788ccec4e1818b3f02d32fe8b5ab9caac52b0962e98466d980710c47298c" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="org.antlr" name="antlr4-runtime" version="4.11.1">
<artifact name="antlr4-runtime-4.11.1.jar">
<sha256 value="e06c6553c1ccc14d36052ec4b0fc6f13b808cf957b5b1dc3f61bf401996ada59" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.antlr" name="antlr4-runtime" version="4.7.2">
<artifact name="antlr4-runtime-4.7.2.jar">
<sha256 value="4c518b87d4bdff8b44cd8cbc1af816e944b62a3fe5b80b781501cf1f4759bbc4" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache" name="apache" version="13">
<artifact name="apache-13.pom">
<sha256 value="ff513db0361fd41237bef4784968bc15aae478d4ec0a9496f811072ccaf3841d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache" name="apache" version="15">
<artifact name="apache-15.pom">
<sha256 value="36c2f2f979ac67b450c0cb480e4e9baf6b40f3a681f22ba9692287d1139ad494" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache" name="apache" version="18">
<artifact name="apache-18.pom">
<sha256 value="7831307285fd475bbc36b20ae38e7882f11c3153b1d5930f852d44eda8f33c17" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache" name="apache" version="19">
<artifact name="apache-19.pom">
<sha256 value="91f7a33096ea69bac2cbaf6d01feb934cac002c48d8c8cfa9c240b40f1ec21df" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache" name="apache" version="21">
<artifact name="apache-21.pom">
<sha256 value="af10c108da014f17cafac7b52b2b4b5a3a1c18265fa2af97a325d9143537b380" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache" name="apache" version="23">
<artifact name="apache-23.pom">
<sha256 value="bc10624e0623f36577fac5639ca2936d3240ed152fb6d8d533ab4d270543491c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache" name="apache" version="9">
<artifact name="apache-9.pom">
<sha256 value="4946e60a547c8eda69f3bc23c5b6f0dadcf8469ea49b1d1da7de34aecfcf18dd" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.apache.ant" name="ant" version="1.10.13">
<artifact name="ant-1.10.13.jar">
<sha256 value="befbfc79e744e9892cfa7db96df3b6e82dc17d2571af42aa427976fc22299838" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.apache.ant" name="ant-launcher" version="1.10.13">
<artifact name="ant-launcher-1.10.13.jar">
<sha256 value="cd7695b3bfb6964ab71b6a0b31dad60005ae77fe502132364679aacf08f77970" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
<component group="org.apache.commons" name="commons-compress" version="1.18">
<artifact name="commons-compress-1.18.jar">
<sha256 value="5f2df1e467825e4cac5996d44890c4201c000b43c0b23cffc0782d28a0beb9b0" origin="Generated by Gradle"/>
</artifact>
<artifact name="commons-compress-1.18.pom">
<sha256 value="672c5fe92bd3eab43e8d53338cad5ca073b6529de4eb2b38859a3eaa6c9e8119" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="org.apache.commons" name="commons-compress" version="1.21">
<artifact name="commons-compress-1.21.jar">
<sha256 value="6aecfd5459728a595601cfa07258d131972ffc39b492eb48bdd596577a2f244a" origin="Generated by Gradle"/>
</artifact>
<artifact name="commons-compress-1.21.pom">
<sha256 value="675bb023c9beedde3232949979b9742a5fea946280a55a1b462d4ca7801088cd" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.commons" name="commons-lang3" version="3.11">
<artifact name="commons-lang3-3.11.jar">
<sha256 value="4ee380259c068d1dbe9e84ab52186f2acd65de067ec09beff731fca1697fdb16" origin="Generated by Gradle"/>
</artifact>
<artifact name="commons-lang3-3.11.pom">
<sha256 value="980d665d83fed04665134f0578e507442a0e750691073784391b0a7988724a75" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.apache.commons" name="commons-lang3" version="3.12.0">
<artifact name="commons-lang3-3.12.0.jar">
<sha256 value="d919d904486c037f8d193412da0c92e22a9fa24230b9d67a57855c5c31c7e94e" origin="Generated by Gradle"/>
</artifact>
<artifact name="commons-lang3-3.12.0.pom">
<sha256 value="82d31f1dcc4583effd744e979165b16da64bf86bca623fc5d1b03ed94f45c85a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.commons" name="commons-parent" version="34">
<artifact name="commons-parent-34.pom">
<sha256 value="3a2e69d06d641d1f3b293126dc9e2e4ea6563bf8c36c87e0ab6fa4292d04b79c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.commons" name="commons-parent" version="35">
<artifact name="commons-parent-35.pom">
<sha256 value="7098a1ab8336ecd4c9dc21cbbcac869f82c66f64b8ac4f7988d41b4fcb44e49a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.commons" name="commons-parent" version="42">
<artifact name="commons-parent-42.pom">
<sha256 value="cd313494c670b483ec256972af1698b330e598f807002354eb765479f604b09c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.commons" name="commons-parent" version="47">
<artifact name="commons-parent-47.pom">
<sha256 value="8a8ecb570553bf9f1ffae211a8d4ca9ee630c17afe59293368fba7bd9b42fcb7" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.commons" name="commons-parent" version="48">
<artifact name="commons-parent-48.pom">
<sha256 value="1e1f7de9370a7b7901f128f1dacd1422be74e3f47f9558b0f79e04c0637ca0b4" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.commons" name="commons-parent" version="51">
<artifact name="commons-parent-51.pom">
<sha256 value="9b779d18b22d8de559605558e7bb0a0a31b3f00c2abb9c878117c398aacabeca" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="org.apache.commons" name="commons-parent" version="52">
<artifact name="commons-parent-52.pom">
<sha256 value="75dbe8f34e98e4c3ff42daae4a2f9eb4cbcd3b5f1047d54460ace906dbb4502e" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.httpcomponents" name="httpclient" version="4.5.12">
<artifact name="httpclient-4.5.12.jar">
<sha256 value="bc5f065aba5dd815ee559dd24d9bcb797fb102ff9cfa036f5091ebc529bd3b93" origin="Generated by Gradle"/>
</artifact>
<artifact name="httpclient-4.5.12.pom">
<sha256 value="419ad1b24a77baa2288ab60ae057b4cf78dbc2c11d27c7204d5cb6779a451527" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.httpcomponents" name="httpclient" version="4.5.13">
<artifact name="httpclient-4.5.13.jar">
<sha256 value="6fe9026a566c6a5001608cf3fc32196641f6c1e5e1986d1037ccdbd5f31ef743" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.httpcomponents" name="httpclient" version="4.5.5">
<artifact name="httpclient-4.5.5.jar">
<sha256 value="7e97724443ad2a25ad8c73183431d47cc7946271bcbbdfa91a8a17522a566573" origin="Generated by Gradle"/>
</artifact>
<artifact name="httpclient-4.5.5.pom">
<sha256 value="db3b0198e11f3aa5fa51310c915b818c134a8cbcb82fc81ddf95ba2313862626" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcomponents-client" version="4.5.12">
<artifact name="httpcomponents-client-4.5.12.pom">
<sha256 value="8f889a53593c027bea003fdbe89399546d7beefa1f60e1756015f10f502b016a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcomponents-client" version="4.5.5">
<artifact name="httpcomponents-client-4.5.5.pom">
<sha256 value="1445d012158f941731a6062c7eab740093ea2745b46b54de236b3f7787e99bf3" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcomponents-core" version="4.4.13">
<artifact name="httpcomponents-core-4.4.13.pom">
<sha256 value="c554e7008e4517c7ef54e005cc8b74f4c87a54a0ea2c6f57be5d0569df51936b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcomponents-core" version="4.4.9">
<artifact name="httpcomponents-core-4.4.9.pom">
<sha256 value="32e66095a919456fc76a10c7865e70c9a14c62bbba847026420a055652366b18" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcomponents-parent" version="10">
<artifact name="httpcomponents-parent-10.pom">
<sha256 value="caaf967d94afb21753f36082c6086206bd1f48825ff596932cceba72b65d39fa" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcomponents-parent" version="11">
<artifact name="httpcomponents-parent-11.pom">
<sha256 value="a901f87b115c55070c7ee43efff63e20e7b02d30af2443ae292bf1f4e532d3aa" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.httpcomponents" name="httpcomponents-parent" version="12">
<artifact name="httpcomponents-parent-12.pom">
<sha256 value="4209f09593212987c29d6801917309dd5e6f71b53b2b1d0e0f0efb984ad11fa1" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.httpcomponents" name="httpcomponents-parent" version="9">
<artifact name="httpcomponents-parent-9.pom">
<sha256 value="2656c7e40bdbe6b6f958798f7d6918b50b544df0e23b52ce3731b9ccc20b5f8c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcore" version="4.4.13">
<artifact name="httpcore-4.4.13.jar">
<sha256 value="e06e89d40943245fcfa39ec537cdbfce3762aecde8f9c597780d2b00c2b43424" origin="Generated by Gradle"/>
</artifact>
<artifact name="httpcore-4.4.13.pom">
<sha256 value="8f812d9fa7b72a3d4aa7f825278932a5df344b42a6d8398905879431a1bf9a97" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents" name="httpcore" version="4.4.9">
<artifact name="httpcore-4.4.9.jar">
<sha256 value="1b4a1c0b9b4222eda70108d3c6e2befd4a6be3d9f78ff53dd7a94966fdf51fc5" origin="Generated by Gradle"/>
</artifact>
<artifact name="httpcore-4.4.9.pom">
<sha256 value="6e94bd777beedeff9b5e770cf654b530325781034b2746c632b131ec74ad513c" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="org.apache.httpcomponents.client5" name="httpclient5" version="5.1.3">
<artifact name="httpclient5-5.1.3.jar">
<sha256 value="28c759254f4e35319e078bb6ffea75676608dc12cb243b24fb3c8732522977fe" origin="Generated by Gradle"/>
</artifact>
</component>
update to monero-java v0.7.13 remove old dependencies from verification-metadata.xml
2023-04-02 21:06:59 +00:00
<component group="org.apache.httpcomponents.client5" name="httpclient5" version="5.2.1">
<artifact name="httpclient5-5.2.1.jar">
<sha256 value="9355f3876baf82fec13ced22c12b62d57536230836406d359459128e4f73ed51" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.httpcomponents.client5" name="httpclient5-parent" version="5.0">
<artifact name="httpclient5-parent-5.0.pom">
<sha256 value="0765e5534209b92e17efd93eee94348cf6de7f3045723d12d0818884b9fab028" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.httpcomponents.client5" name="httpclient5-parent" version="5.1.2">
<artifact name="httpclient5-parent-5.1.2.pom">
<sha256 value="2f4cf51511a2763343aade62e8ad51e95be32d643341aee7902f68bdd5914c2e" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.httpcomponents.core5" name="httpcore5" version="5.1.3">
<artifact name="httpcore5-5.1.3.jar">
<sha256 value="f2bf2f2c7772169c9e30699719667ad30f9b46c4e9d7841907deb2d12d9923fe" origin="Generated by Gradle"/>
</artifact>
</component>
update to monero-java v0.7.13 remove old dependencies from verification-metadata.xml
2023-04-02 21:06:59 +00:00
<component group="org.apache.httpcomponents.core5" name="httpcore5" version="5.2">
<artifact name="httpcore5-5.2.jar">
<sha256 value="293321cbf594d79ea8a0cb0214f75f146d17f088be17ad5ce11c2fe864df124c" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.httpcomponents.core5" name="httpcore5-h2" version="5.1.3">
<artifact name="httpcore5-h2-5.1.3.jar">
<sha256 value="d0e78ba15aa8ebe77982b660ac4b09a95d6e035dbdbea762577dc1c8e2935807" origin="Generated by Gradle"/>
</artifact>
update to monero-java v0.7.13 remove old dependencies from verification-metadata.xml
2023-04-02 21:06:59 +00:00
</component>
<component group="org.apache.httpcomponents.core5" name="httpcore5-h2" version="5.2">
<artifact name="httpcore5-h2-5.2.jar">
<sha256 value="5a087fb8c619979d492a83546f351ddadf32b28cc6a32923229f3fc777171578" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.httpcomponents.core5" name="httpcore5-parent" version="5.0">
<artifact name="httpcore5-parent-5.0.pom">
<sha256 value="b0dfd9fdc009aa5ca9a737ad9e4bef258f7dc32c0589f1dee0465bbc1a280864" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.httpcomponents.core5" name="httpcore5-parent" version="5.1.3">
<artifact name="httpcore5-parent-5.1.3.pom">
<sha256 value="a67538865ae0f3744b21e91ca47d461054737c552d1ff29da714c860c992d5bb" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="org.apache.logging" name="logging-parent" version="3">
<artifact name="logging-parent-3.pom">
<sha256 value="763a2ec2b8094d4161deb6c264b1262085b9be30bf3a31c2ce137242e57722a7" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.logging.log4j" name="log4j" version="2.17.0">
<artifact name="log4j-2.17.0.pom">
<sha256 value="8704606faeb779d6d2904f02ca616e0b981fe389d9fe9b89ec84a1e42aee81d2" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.logging.log4j" name="log4j-api" version="2.11.0">
<artifact name="log4j-api-2.11.0.jar">
<sha256 value="fa5828950269b0ae425c96d889f18f40b336e9fa886841ae06bb9225511f1217" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.logging.log4j" name="log4j-api" version="2.17.0">
<artifact name="log4j-api-2.17.0.jar">
<sha256 value="ab9cadc80e234580e3f3c8c18644314fccd4b3cd3f7085d4e934866cb561b95d" origin="Generated by Gradle"/>
</artifact>
<artifact name="log4j-api-2.17.0.pom">
<sha256 value="6422d9af59acb0077e8a91c7c34a4062ff56a9731c34836a72427084e27aa479" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.apache.logging.log4j" name="log4j-api" version="2.20.0">
<artifact name="log4j-api-2.20.0.jar">
<sha256 value="2f43eea679ea66f14ca0f13fec2a8600ac124f5a5231dcb4df8393eddcb97550" origin="Generated by Gradle"/>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.apache.logging.log4j" name="log4j-core" version="2.20.0">
<artifact name="log4j-core-2.20.0.jar">
<sha256 value="6137df848cdaed9f4d5076f75513c6c85da80b953f4e7acca38098b770763f55" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
<component group="org.apache.logging.log4j" name="log4j-to-slf4j" version="2.17.0">
<artifact name="log4j-to-slf4j-2.17.0.jar">
<sha256 value="df8a9a9d06368a87abd04051597310cc7a501762ab0cd7492ba106df92862c78" origin="Generated by Gradle"/>
</artifact>
<artifact name="log4j-to-slf4j-2.17.0.pom">
<sha256 value="24d195ba852929def67345ea9c2a52e6d6d470b86bee3a2fd64e087fe5a0151b" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.tomcat" name="tomcat-annotations-api" version="8.5.27">
<artifact name="tomcat-annotations-api-8.5.27.jar">
<sha256 value="4d14fbc57f488c49055c0803ec84de036f1c34f9b51e05fda5313d79ddd1e73c" origin="Generated by Gradle"/>
</artifact>
<artifact name="tomcat-annotations-api-8.5.27.pom">
<sha256 value="28ffbcd1dadf6223d0a51ff108f2976fbc85bb5651ea6cb6e4ed5ffc7ea1878d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.tomcat.embed" name="tomcat-embed-core" version="8.5.27">
<artifact name="tomcat-embed-core-8.5.27.jar">
<sha256 value="9ef733f04908b3921ee5d24cddd73b478fd6a935273153dc8d62df728667d554" origin="Generated by Gradle"/>
</artifact>
<artifact name="tomcat-embed-core-8.5.27.pom">
<sha256 value="eeec6fbf6b0fe7f0ba64703122409157a802f82ef98b57ea29e1df3d3340bf71" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.tomcat.embed" name="tomcat-embed-core" version="9.0.56">
<artifact name="tomcat-embed-core-9.0.56.jar">
<sha256 value="17d020617f6be1b792ff4a7516ae71b0928ea73e0d9845f13c244d95d015f5fa" origin="Generated by Gradle"/>
</artifact>
<artifact name="tomcat-embed-core-9.0.56.pom">
<sha256 value="d1205ac1d8bc38579eea402f16ba13011f8972ff31119706324a0173015abb9b" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.tomcat.embed" name="tomcat-embed-el" version="8.5.27">
<artifact name="tomcat-embed-el-8.5.27.jar">
<sha256 value="cc05a14bc36fc23773ca49375f08816ae8121e7bcc94cccf2e642854f1285faf" origin="Generated by Gradle"/>
</artifact>
<artifact name="tomcat-embed-el-8.5.27.pom">
<sha256 value="203bf3bb5e9c5b73d14fb1503fc1e03984eeb85f12942a8aac51eba188534a0f" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.tomcat.embed" name="tomcat-embed-el" version="9.0.56">
<artifact name="tomcat-embed-el-9.0.56.jar">
<sha256 value="3f7fc3bf1c76c28e6b47255f65c983f8ded67576060ee1dd7a548f8659b26bef" origin="Generated by Gradle"/>
</artifact>
<artifact name="tomcat-embed-el-9.0.56.pom">
<sha256 value="e3298f69048ce9b151f3d0f05b097ce902d4e1b2bb6b54f970bcd8505115545a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apache.tomcat.embed" name="tomcat-embed-websocket" version="8.5.27">
<artifact name="tomcat-embed-websocket-8.5.27.jar">
<sha256 value="a1cb58b1ce98dc2fdcf34f342d704bd7d13f3f3e3b0b7730a1be85f9d573ec82" origin="Generated by Gradle"/>
</artifact>
<artifact name="tomcat-embed-websocket-8.5.27.pom">
<sha256 value="40bc4e976a72fcc1d2c2f5e81c4760828fbd18a37ace1e91926edcd1edb1afcc" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apache.tomcat.embed" name="tomcat-embed-websocket" version="9.0.56">
<artifact name="tomcat-embed-websocket-9.0.56.jar">
<sha256 value="d78145d4d87880e2b0403cad49f41cc289ad2d89be50ca494ae22edd61283e73" origin="Generated by Gradle"/>
</artifact>
<artifact name="tomcat-embed-websocket-9.0.56.pom">
<sha256 value="31a52511454d940bb0f0d623baf021edd87f3be1098edea0b81f9dfa60f962de" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.apiguardian" name="apiguardian-api" version="1.1.0">
<artifact name="apiguardian-api-1.1.0.jar">
<sha256 value="a9aae9ff8ae3e17a2a18f79175e82b16267c246fbbd3ca9dfbbb290b08dcfdd4" origin="Generated by Gradle"/>
</artifact>
<artifact name="apiguardian-api-1.1.0.pom">
<sha256 value="a945b9cb5cd9b77b2c711844e659c43ec070ef59d9f509fa9f4c1861b4862711" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.apiguardian" name="apiguardian-api" version="1.1.2">
<artifact name="apiguardian-api-1.1.2.jar">
<sha256 value="b509448ac506d607319f182537f0b35d71007582ec741832a1f111e5b5b70b38" origin="Generated by Gradle"/>
</artifact>
</component>
general rebase in order to update payment methods and desktop app Co-authored-by: Alva Swanson <alvasw@protonmail.com> Co-authored-by: andyheko <haoen.ko@gmail.com> Co-authored-by: Bisq GitHub Admin <51445974+bisq-github-admin-3@users.noreply.github.com> Co-authored-by: BtcContributor <79100296+BtcContributor@users.noreply.github.com> Co-authored-by: cd2357 <cd2357@users.noreply.github.com> Co-authored-by: chimp1984 <chimp1984@gmx.com> Co-authored-by: Chris Beams <chris@beams.io> Co-authored-by: Christoph Atteneder <christoph.atteneder@gmail.com> Co-authored-by: Devin Bileck <603793+devinbileck@users.noreply.github.com> Co-authored-by: ghubstan <36207203+ghubstan@users.noreply.github.com> Co-authored-by: Huey <hueydane@gmail.com> Co-authored-by: Jakub Loucký <jakub.loucky@outlook.cz> Co-authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com> Co-authored-by: KanoczTomas <tomas.kanocz@cnl.sk> Co-authored-by: m52go <735155+m52go@users.noreply.github.com> Co-authored-by: Marcus0x <marcus0x@xrhodium.org> Co-authored-by: MarnixCroes <93143998+MarnixCroes@users.noreply.github.com> Co-authored-by: Martin Harrigan <martinharrigan@gmail.com> Co-authored-by: MwithM <50149324+MwithM@users.noreply.github.com> Co-authored-by: sqrrm <sqrrm@users.noreply.github.com> Co-authored-by: Stan <36207203+ghubstan@users.noreply.github.com> Co-authored-by: Stephan Oeste <emzy@emzy.de> Co-authored-by: Steven Barclay <stejbac@gmail.com> Co-authored-by: WAT <shiido.it@gmail.com> Co-authored-by: wiz <j@wiz.biz> Co-authored-by: xyzmaker123 <84982606+xyzmaker123@users.noreply.github.com>
2022-05-26 17:42:10 +00:00
<component group="org.bitbucket.cowwoc" name="diff-match-patch" version="1.2">
<artifact name="diff-match-patch-1.2.jar">
<sha256 value="1c9debaa96aa26a6f057723380a4c1f5d9734c429bdb34cb2090da39b9cf2c62" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.bouncycastle" name="bcpg-jdk15on" version="1.63">
<artifact name="bcpg-jdk15on-1.63.jar">
<sha256 value="dc4f51adfc46583c2543489c82708fef5660202bf264c7cd453f081a117ea536" origin="Generated by Gradle"/>
</artifact>
<artifact name="bcpg-jdk15on-1.63.pom">
<sha256 value="4a95f001cbf1a5c333db567ec04f54875e3b12abadc23c69d808b4014559a5d4" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.bouncycastle" name="bcprov-jdk15on" version="1.63">
<artifact name="bcprov-jdk15on-1.63.jar">
<sha256 value="28155c8695934f666fabc235f992096e40d97ecb044d5b6b0902db6e15a0b72f" origin="Generated by Gradle"/>
</artifact>
<artifact name="bcprov-jdk15on-1.63.pom">
<sha256 value="db018a103911a5f3c9762b95483b6b9c875b34d2595b867069ec00567495307c" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.bouncycastle" name="bcprov-jdk15to18" version="1.63">
<artifact name="bcprov-jdk15to18-1.63.jar">
<sha256 value="82c28318b178da751d174b1adf6c43e0199f0fcf80a7bf6483caa226ae0d30b3" origin="Generated by Gradle"/>
</artifact>
<artifact name="bcprov-jdk15to18-1.63.pom">
<sha256 value="40bc5efb0aa8ecb08d180edb4758255648877df6fd44ef0815db960a6c4d828f" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.checkerframework" name="checker-compat-qual" version="2.5.5">
<artifact name="checker-compat-qual-2.5.5.jar">
<sha256 value="11d134b245e9cacc474514d2d66b5b8618f8039a1465cdc55bbc0b34e0008b7a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.checkerframework" name="checker-qual" version="2.10.0">
<artifact name="checker-qual-2.10.0.jar">
<sha256 value="d261fde25d590f6b69db7721d469ac1b0a19a17ccaaaa751c31f0d8b8260b894" origin="Generated by Gradle"/>
</artifact>
<artifact name="checker-qual-2.10.0.pom">
<sha256 value="246e47e395f8d7a8c12b7222b166bc3a1d3809bc3a3d30de97470aa38d952a4b" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.checkerframework" name="checker-qual" version="2.5.2">
<artifact name="checker-qual-2.5.2.jar">
<sha256 value="64b02691c8b9d4e7700f8ee2e742dce7ea2c6e81e662b7522c9ee3bf568c040a" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="org.checkerframework" name="checker-qual" version="3.27.0">
<artifact name="checker-qual-3.27.0.jar">
<sha256 value="25fda6f3eb2ee2139ff5d7d3992667d526ebf1b0fb87df36fc75aa35679e6dab" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.checkerframework" name="checker-qual" version="3.8.0">
<artifact name="checker-qual-3.8.0.jar">
<sha256 value="c88c2e6a5fdaeb9f26fcf879264042de8a9ee9d376e2477838feaabcfa44dda6" origin="Generated by Gradle"/>
</artifact>
<artifact name="checker-qual-3.8.0.pom">
<sha256 value="7e6d59e2d3bc01b1f04fa3667193a6d4170199b14fba53a7a8e36bf7602239a7" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-bom" version="3.0.9">
<artifact name="groovy-bom-3.0.9.pom">
<sha256 value="bf84aecc75ea2f8b526a64367a46e09e7421a441a5443b9cda444a85cc926775" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.codehaus.jackson" name="jackson-core-asl" version="1.9.11">
<artifact name="jackson-core-asl-1.9.11.jar">
<sha256 value="5fb6924b888550a9b0e8420747a93cc4ad24e03e724dcf4934c30cc0c4882ffc" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.codehaus.mojo" name="animal-sniffer-annotations" version="1.17">
<artifact name="animal-sniffer-annotations-1.17.jar">
<sha256 value="92654f493ecfec52082e76354f0ebf87648dc3d5cec2e3c3cdb947c016747a53" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.codehaus.plexus" name="plexus-utils" version="3.5.1">
<artifact name="plexus-utils-3.5.1.jar">
<sha256 value="86e0255d4c879c61b4833ed7f13124e8bb679df47debb127326e7db7dd49a07b" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.eclipse.ee4j" name="project" version="1.0.5">
<artifact name="project-1.0.5.pom">
<sha256 value="916b4794d8d8220a59a3fdf6a64dbe794aeb23395e888b81ae36a9b5a2c591a6" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.ee4j" name="project" version="1.0.6">
<artifact name="project-1.0.6.pom">
<sha256 value="4e7d8329d8da7dcf30779d824241be145f27108932f5a5a24eb907677bc8d72d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-bom" version="9.4.44.v20210927">
<artifact name="jetty-bom-9.4.44.v20210927.pom">
<sha256 value="ece9c6b71303d8d73cfa351c6ea5399e18ab04436e1f6320769644514a7bf1d6" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.eclipse.jetty" name="jetty-http" version="9.3.6.v20151106">
<artifact name="jetty-http-9.3.6.v20151106.jar">
<sha256 value="f0bb475e064671ccd75fc89edae5f3f718139189e5e09e672cb4fc3784215d1b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-io" version="9.3.6.v20151106">
<artifact name="jetty-io-9.3.6.v20151106.jar">
<sha256 value="8ece9bf183c6c2d6c5036d7664d450cf9897f0e5aacb8f3dae092db7cf7848ec" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-security" version="9.3.6.v20151106">
<artifact name="jetty-security-9.3.6.v20151106.jar">
<sha256 value="d9729341568a245f3c028991c328e5fce35294f026fdfb9e2ab628ff34975fb5" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-server" version="9.3.6.v20151106">
<artifact name="jetty-server-9.3.6.v20151106.jar">
<sha256 value="2277b6211e1db363d0cb22317f49906cd906dd47ca93f397cffead618dc052ea" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-servlet" version="9.3.6.v20151106">
<artifact name="jetty-servlet-9.3.6.v20151106.jar">
<sha256 value="4aabcb8c4b32918cdc66f6b4e48ba08276559f3d3eba6919cb49c221d08bb7f9" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-util" version="9.3.6.v20151106">
<artifact name="jetty-util-9.3.6.v20151106.jar">
<sha256 value="3149d7cb665e3b7a37809fb9915a4c4ef190ec3d2d80d6c15207bde075224304" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-webapp" version="9.3.6.v20151106">
<artifact name="jetty-webapp-9.3.6.v20151106.jar">
<sha256 value="2e1805b52831dc88d2c19f1ee660609f337e2ec3007c9931dac65b7867f4aff1" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty" name="jetty-xml" version="9.3.6.v20151106">
<artifact name="jetty-xml-9.3.6.v20151106.jar">
<sha256 value="58a7c092323e9bff29fa7cd9ca072f5d7fb8e5806342c941b9780c5cbfcaf112" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty.websocket" name="websocket-api" version="9.3.6.v20151106">
<artifact name="websocket-api-9.3.6.v20151106.jar">
<sha256 value="541a2c575082b6eec72a2ac59d7397301c41991978768b6b5c9d261ec9a25755" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty.websocket" name="websocket-client" version="9.3.6.v20151106">
<artifact name="websocket-client-9.3.6.v20151106.jar">
<sha256 value="c4e74f5b2b9ec4b71ecc5c852039f5f43101d0b7332b9c95924591c633427518" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty.websocket" name="websocket-common" version="9.3.6.v20151106">
<artifact name="websocket-common-9.3.6.v20151106.jar">
<sha256 value="df209f43c7d4485263088d1947e9ef20b450218b1c520c14654dcf25b0bd0793" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty.websocket" name="websocket-server" version="9.3.6.v20151106">
<artifact name="websocket-server-9.3.6.v20151106.jar">
<sha256 value="cfe658a601eff23ee151c03672ad838388365f79d98556a04be130ac7c11cf4d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.eclipse.jetty.websocket" name="websocket-servlet" version="9.3.6.v20151106">
<artifact name="websocket-servlet-9.3.6.v20151106.jar">
<sha256 value="fa8d1146605c66b732d5c03066800fee63e4822cde688d189db4a336a442f412" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.fxmisc.easybind" name="easybind" version="1.0.3">
<artifact name="easybind-1.0.3.jar">
<sha256 value="666af296dda6de68751668a62661571b5238ac6f1c07c8a204fc6f902b222aaf" origin="Generated by Gradle"/>
</artifact>
<artifact name="easybind-1.0.3.pom">
<sha256 value="28323c619c05bd0ef05bae81cd056b04f382d7d09ae9e46311e4ec828b611f2a" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.glassfish.jersey" name="jersey-bom" version="2.35">
<artifact name="jersey-bom-2.35.pom">
<sha256 value="10d308e9c4cda17c348e78fa5db762a42b062476e3f0a2fdf084c171e286d087" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.hamcrest" name="hamcrest" version="2.2">
<artifact name="hamcrest-2.2.jar">
<sha256 value="5e62846a89f05cd78cd9c1a553f340d002458380c320455dd1f8fc5497a8a1c1" origin="Generated by Gradle"/>
</artifact>
<artifact name="hamcrest-2.2.pom">
<sha256 value="b36137376c4b3fcf76dc337e2a1bc5b691a2ac1aa966ab5d26209a93812fa57d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.hamcrest" name="hamcrest-all" version="1.3">
<artifact name="hamcrest-all-1.3.jar">
<sha256 value="4877670629ab96f34f5f90ab283125fcd9acb7e683e66319a68be6eb2cca60de" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.hamcrest" name="hamcrest-core" version="1.3">
<artifact name="hamcrest-core-1.3.jar">
<sha256 value="66fdef91e9739348df7a096aa384a5685f4e875584cce89386a7a47251c4d8e9" origin="Generated by Gradle"/>
</artifact>
<artifact name="hamcrest-core-1.3.pom">
<sha256 value="fde386a7905173a1b103de6ab820727584b50d0e32282e2797787c20a64ffa93" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.hamcrest" name="hamcrest-core" version="2.2">
<artifact name="hamcrest-core-2.2.jar">
<sha256 value="094f5d92b4b7d9c8a2bf53cc69d356243ae89c3499457bcb4b92f7ed3bf95879" origin="Generated by Gradle"/>
</artifact>
<artifact name="hamcrest-core-2.2.pom">
<sha256 value="f7fde2fff5101a5fc3a39e28810b911c2da202ddc2bd50765f89e7c6ff8ce7dd" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.hamcrest" name="hamcrest-parent" version="1.3">
<artifact name="hamcrest-parent-1.3.pom">
<sha256 value="6d535f94efb663bdb682c9f27a50335394688009642ba7a9677504bc1be4129b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.hibernate" name="hibernate-validator" version="5.3.6.Final">
<artifact name="hibernate-validator-5.3.6.Final.jar">
<sha256 value="bc73804bd1dca71d7b2c2696d239720a654b34d46ff172516ecdac1f26adccb4" origin="Generated by Gradle"/>
</artifact>
<artifact name="hibernate-validator-5.3.6.Final.pom">
<sha256 value="76d0c4c60709dcc09cb81f687b3920500fc3f5eaf10cddea4fb8c2b209057788" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.hibernate" name="hibernate-validator-parent" version="5.3.6.Final">
<artifact name="hibernate-validator-parent-5.3.6.Final.pom">
<sha256 value="914d147f43944fee3be0e3dd4a6903cf15f1ad54f69fa6108ffd56dd3c022140" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.infinispan" name="infinispan-bom" version="12.1.11.Final">
<artifact name="infinispan-bom-12.1.11.Final.pom">
<sha256 value="8bb19b91c54ef90a53c4be21a11dcab92c40fc67105d6d26ee5daa408d69fe35" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.infinispan" name="infinispan-build-configuration-parent" version="12.1.11.Final">
<artifact name="infinispan-build-configuration-parent-12.1.11.Final.pom">
<sha256 value="e22cd7e20bebaa53f9fc3b5631e550c740d480ada56e0d1cd85e236a37e95c2c" origin="Generated by Gradle"/>
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="org.jacoco" name="org.jacoco.agent" version="0.8.10">
<artifact name="org.jacoco.agent-0.8.10.jar">
<sha256 value="32d62211c0a323f50822a750a647c122b2b1b559f63533ea2e324c0324381370" origin="Generated by Gradle"/>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="org.jacoco" name="org.jacoco.ant" version="0.8.10">
<artifact name="org.jacoco.ant-0.8.10.jar">
<sha256 value="a7c8dd6741acb337cc0771a9bf176aa67c09a52a6de011eb7a0f5e78c9bd5872" origin="Generated by Gradle"/>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="org.jacoco" name="org.jacoco.core" version="0.8.10">
<artifact name="org.jacoco.core-0.8.10.jar">
<sha256 value="e789667d93a7503938ee978ae4fbbc9a1bccda3b546299b24d8550d816d80e08" origin="Generated by Gradle"/>
Revert "Support for open JDK 20 by updating dependencies" This reverts commit 5923a34ef9c9ff23b37195ba1c95108e8ac175ef.
2023-07-11 13:57:22 +00:00
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="org.jacoco" name="org.jacoco.report" version="0.8.10">
<artifact name="org.jacoco.report-0.8.10.jar">
<sha256 value="3e35c14f7853c7c88dbe04cf086ee053a5739f419e98009909bbedecddddd50c" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="org.javassist" name="javassist" version="3.28.0-GA">
<artifact name="javassist-3.28.0-GA.jar">
<sha256 value="57d0a9e9286f82f4eaa851125186997f811befce0e2060ff0a15a77f5a9dd9a7" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.jboss" name="jboss-parent" version="15">
<artifact name="jboss-parent-15.pom">
<sha256 value="2ea302319636da65ee4566f956fe9f8328caff84fb4eeb1f9f472821a7e4bc29" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.jboss" name="jboss-parent" version="36">
<artifact name="jboss-parent-36.pom">
<sha256 value="000dd616298aebd21a9d5731874df083d7298424b91e037b73cbdd07ebc83e0e" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.jboss.arquillian" name="arquillian-bom" version="1.1.11.Final">
<artifact name="arquillian-bom-1.1.11.Final.pom">
<sha256 value="e40b764f02bfd8b46ee8ee1b4b6ba4a7d4d5989fab1b88fec7c507a4335aa985" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.jboss.logging" name="jboss-logging" version="3.3.1.Final">
<artifact name="jboss-logging-3.3.1.Final.jar">
<sha256 value="9f7d8b884370763b131bf48a0fc91edec89ad80e0e40c47658098a686a905bb2" origin="Generated by Gradle"/>
</artifact>
<artifact name="jboss-logging-3.3.1.Final.pom">
<sha256 value="6b7f80b374b17463939f9a6b14b289a095c43f2e11ba2a73d5e1c71ad059d800" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.jboss.shrinkwrap" name="shrinkwrap-bom" version="1.2.3">
<artifact name="shrinkwrap-bom-1.2.3.pom">
<sha256 value="a1e6090cbb406d6667fd77b6487718aa6b7dbb04686525e6629d04918cd27a69" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.jboss.shrinkwrap.descriptors" name="shrinkwrap-descriptors-bom" version="2.0.0-alpha-8">
<artifact name="shrinkwrap-descriptors-bom-2.0.0-alpha-8.pom">
<sha256 value="f0d28c0d4f4d542e17d6a05f2326de707fa31c55066b6e35889863467323c112" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.jboss.shrinkwrap.resolver" name="shrinkwrap-resolver-bom" version="2.2.0">
<artifact name="shrinkwrap-resolver-bom-2.2.0.pom">
<sha256 value="77f4b8f7e272c5f37093abf697b3069d1de82f4a863c045eb0fe1aedef3e6dcc" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.jdom" name="jdom2" version="2.0.6.1">
<artifact name="jdom2-2.0.6.1.jar">
<sha256 value="0b20f45e3a0fd8f0d12cdc5316b06776e902b1365db00118876f9175c60f302c" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
<component group="org.jetbrains" name="annotations" version="13.0">
<artifact name="annotations-13.0.jar">
<sha256 value="ace2a10dc8e2d5fd34925ecac03e4988b2c0f851650c94b8cef49ba1bd111478" origin="Generated by Gradle"/>
</artifact>
<artifact name="annotations-13.0.pom">
<sha256 value="965aeb2bedff369819bdde1bf7a0b3b89b8247dd69c88b86375d76163bb8c397" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-bom" version="1.6.10">
<artifact name="kotlin-bom-1.6.10.pom">
<sha256 value="4af984a6afb23d961293ac2d7a51027a12fe46193d37df39e88d0dfddfeeeaba" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib" version="1.3.41">
<artifact name="kotlin-stdlib-1.3.41.jar">
<sha256 value="6ea3d0921b26919b286f05cbdb906266666a36f9a7c096197114f7495708ffbc" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-1.3.41.pom">
<sha256 value="785b5b66f1146317d5ed5b18c8e0c10f83cd5c909434c799a4da9823f028cd63" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib" version="1.6.10">
<artifact name="kotlin-stdlib-1.6.10.jar">
<sha256 value="5305f7a4dee7a6cb79a29c258aca93de47b49588a6dfc6da01bd8772589ea66c" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-1.6.10.pom">
<sha256 value="3b08709ea4bae3669d9a29b9e007a8550b10c1516c10a8f6dbe9f94ab81dc46d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib-common" version="1.3.41">
<artifact name="kotlin-stdlib-common-1.3.41.jar">
<sha256 value="6c91dea17d7dce5f0b550c3de3305767e5fb46247b6d1eb7eca0ca1fe18458de" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-common-1.3.41.pom">
<sha256 value="d2e537cd1f7705276242d8cc903a0286b6dc86b41b6e728e967ef719022f2e15" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib-common" version="1.6.10">
<artifact name="kotlin-stdlib-common-1.6.10.jar">
<sha256 value="280ddd0994e4560c9a49ee81c1b047ddc2b8f2176159475066025b474b37effd" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-common-1.6.10.pom">
<sha256 value="f75af217cdd8dd9e07b1e0e018084a32092a091a390b73feaa657ec44e5cf094" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib-jdk7" version="1.3.41">
<artifact name="kotlin-stdlib-jdk7-1.3.41.jar">
<sha256 value="25e2409aba0ec37d2fd7c77727d7835b511879de8d9bf4862af0b493aabbe39e" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-jdk7-1.3.41.pom">
<sha256 value="54c3962d2cf839d41bbee8b4817a6b2d06990c305c2efea655f64973d468a5fd" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib-jdk7" version="1.6.10">
<artifact name="kotlin-stdlib-jdk7-1.6.10.jar">
<sha256 value="2aedcdc6b69b33bdf5cc235bcea88e7cf6601146bb6bcdffdb312bbacd7be261" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-jdk7-1.6.10.pom">
<sha256 value="612211ff930f5b52c724ff763417d5aa281dd7e0325c3b35c8d18120a6a8df4d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib-jdk8" version="1.3.41">
<artifact name="kotlin-stdlib-jdk8-1.3.41.jar">
<sha256 value="f7dbbaee3e0841758187a213c052388a4e619e11c87ab16f4bc229cfe7ce5fed" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-jdk8-1.3.41.pom">
<sha256 value="e3856758c3bb08b7c97ddcd493521c5e0bd0741717c93b292bf1a541513af082" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.jetbrains.kotlin" name="kotlin-stdlib-jdk8" version="1.6.10">
<artifact name="kotlin-stdlib-jdk8-1.6.10.jar">
<sha256 value="1456d82d039ea30d8485b032901f52bbf07e7cdbe8bb1f8708ad32a8574c41ce" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-stdlib-jdk8-1.6.10.pom">
<sha256 value="43a649fa737bfb35fa4af4e6de33e2f08a5d19104d7582ea40dbcd2b63790acc" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.jetbrains.kotlinx" name="kotlinx-coroutines-bom" version="1.5.2">
<artifact name="kotlinx-coroutines-bom-1.5.2.pom">
<sha256 value="495f270a5b16964d898660ca7e4dc2fd65fd5a3754bfe8edd3e631a6b0128981" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.json" name="json" version="20160810">
<artifact name="json-20160810.jar">
<sha256 value="bf51c9013128cb15201225e51476f60ad9116813729040655a238d2829aef8b8" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.junit" name="junit-bom" version="5.7.0">
<artifact name="junit-bom-5.7.0.pom">
<sha256 value="35fb15f8d0bee2b5900a22832762366552f9a349c56ced60ba123ce47738ff00" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.junit" name="junit-bom" version="5.7.1">
<artifact name="junit-bom-5.7.1.pom">
<sha256 value="0b9b14a3d62106fafe8c68a717b87b87ad18685899451b753c04fa41b6857784" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.junit" name="junit-bom" version="5.8.2">
<artifact name="junit-bom-5.8.2.pom">
<sha256 value="836069ca9e8ee3c56e48376222da291263f137bd3fd16d84fdd47efcc3f286e2" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.junit.jupiter" name="junit-jupiter-api" version="5.7.0">
<artifact name="junit-jupiter-api-5.7.0.jar">
<sha256 value="b03f78e0daeed2d77a0af9bcd662b4cdb9693f7ee72e01a539b508b84c63d182" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-jupiter-api-5.7.0.pom">
<sha256 value="a0f823d513c8d4692935f24c2fe6e77cc4a7b6147a9e8a518f722e50bbf86138" origin="Generated by Gradle"/>
</artifact>
</component>
moving away from JUnit 4 completely to JUnit 5 Jupiter
2023-03-25 17:11:58 +00:00
<component group="org.junit.jupiter" name="junit-jupiter-api" version="5.9.2">
<artifact name="junit-jupiter-api-5.9.2.jar">
<sha256 value="f767a170f97127b0ad3582bf3358eabbbbe981d9f96411853e629d9276926fd5" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.junit.jupiter" name="junit-jupiter-engine" version="5.7.0">
<artifact name="junit-jupiter-engine-5.7.0.jar">
<sha256 value="dfa26af94644ac2612dde6625852fcb550a0d21caa243257de54cba738ba87af" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-jupiter-engine-5.7.0.pom">
<sha256 value="b702e250875d331ee3c6b88f37299fbe951f43992f4b2e4a8f144e2e4cf2c7e8" origin="Generated by Gradle"/>
</artifact>
</component>
moving away from JUnit 4 completely to JUnit 5 Jupiter
2023-03-25 17:11:58 +00:00
<component group="org.junit.jupiter" name="junit-jupiter-engine" version="5.9.2">
<artifact name="junit-jupiter-engine-5.9.2.jar">
<sha256 value="74cfc49388f760413ff348ca2c9ab39527484b57deecd157f2275a5f8a5fe971" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.junit.jupiter" name="junit-jupiter-params" version="5.7.0">
<artifact name="junit-jupiter-params-5.7.0.jar">
<sha256 value="ca9f555c37b9bf79effd2e834af549e4feb52ad8ac9e348fe5b430d4d8a482b7" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-jupiter-params-5.7.0.pom">
<sha256 value="23873e305a9751109839ad08b6b37dfadd1036f43b359b3b1b7bd2601fc73260" origin="Generated by Gradle"/>
</artifact>
</component>
moving away from JUnit 4 completely to JUnit 5 Jupiter
2023-03-25 17:11:58 +00:00
<component group="org.junit.jupiter" name="junit-jupiter-params" version="5.9.2">
<artifact name="junit-jupiter-params-5.9.2.jar">
<sha256 value="bde91900a5ce5d6663bb44bc708494b35daefcd73e1bb7afa61a4affe38ea97d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.junit.platform" name="junit-platform-commons" version="1.7.0">
<artifact name="junit-platform-commons-1.7.0.jar">
<sha256 value="5330ee87cc7586e6e25175a34e9251624ff12ff525269d3415d0b4ca519b6fea" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-platform-commons-1.7.0.pom">
<sha256 value="0cd7c4f9bee659912ac1dce46f123cd06f40bbb73ab316bd9411c792e3c680a2" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.junit.platform" name="junit-platform-commons" version="1.8.2">
<artifact name="junit-platform-commons-1.8.2.jar">
<sha256 value="d2e015fca7130e79af2f4608dc54415e4b10b592d77333decb4b1a274c185050" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-platform-commons-1.8.2.pom">
<sha256 value="ce852e34c6a184aa6c80ee8df0471713a7408134134f08e3c1c3dd87c6b59ab7" origin="Generated by Gradle"/>
</artifact>
</component>
moving away from JUnit 4 completely to JUnit 5 Jupiter
2023-03-25 17:11:58 +00:00
<component group="org.junit.platform" name="junit-platform-commons" version="1.9.2">
<artifact name="junit-platform-commons-1.9.2.jar">
<sha256 value="624a3d745ef1d28e955a6a67af8edba0fdfc5c9bad680a73f67a70bb950a683d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.junit.platform" name="junit-platform-engine" version="1.7.0">
<artifact name="junit-platform-engine-1.7.0.jar">
<sha256 value="75f21a20dc594afdc875736725b408cec6d0344874d29f34b2dd3075500236f2" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-platform-engine-1.7.0.pom">
<sha256 value="225b99c5032fd1cb8cecda2e8b5a7526d6a5f81fb98a29a57557f7f5ccda9d12" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.junit.platform" name="junit-platform-engine" version="1.8.2">
<artifact name="junit-platform-engine-1.8.2.jar">
<sha256 value="0b7d000f8c3e8e5f7d6b819649936e7b9938314e87c8f983805218ea57567e59" origin="Generated by Gradle"/>
</artifact>
<artifact name="junit-platform-engine-1.8.2.pom">
<sha256 value="0168643266060ed928ef5a81823003ecfae79a9a8c0bbfd76f4201c6c9d771c5" origin="Generated by Gradle"/>
</artifact>
</component>
moving away from JUnit 4 completely to JUnit 5 Jupiter
2023-03-25 17:11:58 +00:00
<component group="org.junit.platform" name="junit-platform-engine" version="1.9.2">
<artifact name="junit-platform-engine-1.9.2.jar">
<sha256 value="25f23dc535a091e9dc80c008faf29dcb92be902e6911f77a736fbaf019908367" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-binance" version="4.4.2">
<artifact name="xchange-binance-4.4.2.jar">
<sha256 value="751a8cb76d75613ed38440a1a69e3a053e3cf869882b89eb8978b51c497111bb" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-binance-4.4.2.pom">
<sha256 value="90505e8787a734f1b135d92b09d27b022c8920f78debbd0a02e9918f5fec611e" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-binance" version="5.0.13">
<artifact name="xchange-binance-5.0.13.jar">
<sha256 value="be6db4fa53f3009bc5023c62df272e6f4cfbfc6750f4c500b05ed07279dce644" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-binance-5.0.13.pom">
<sha256 value="73b89e77e5d86a5fa0a51a3f6857b4179ea04e670f11218890b48297f6fc35df" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-bitbay" version="4.4.2">
<artifact name="xchange-bitbay-4.4.2.jar">
<sha256 value="723ae277b65cca1c07346cf534de1ab407f62f6990353099a9235eed70e3edcc" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitbay-4.4.2.pom">
<sha256 value="bc88e505a37fbbdcabc55c9bfee452839542a9a425cbd23df8e56574bfddb8de" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-bitbay" version="5.0.13">
<artifact name="xchange-bitbay-5.0.13.jar">
<sha256 value="78f5570682ebb4f775f18389189ad25ca43dc04bdc908ce4113873b750dfa4e2" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitbay-5.0.13.pom">
<sha256 value="7e5f3a26859291a69e427ac9e901f28497ab08c3928a82074495a51a63289941" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-bitfinex" version="4.4.2">
<artifact name="xchange-bitfinex-4.4.2.jar">
<sha256 value="1f7dcb007e4fe04da5a72681a21ce30f7a5071b1a886ce00f58eb8c0e47ea05c" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitfinex-4.4.2.pom">
<sha256 value="dcbf7f137c098488d716a90a76e31bc041df33e2a21e1381caba76b5c80d6118" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-bitfinex" version="5.0.13">
<artifact name="xchange-bitfinex-5.0.13.jar">
<sha256 value="cbb09de59b1a99634ce0b633373caee3543c77fac79093bded1a0d15e02f281c" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitfinex-5.0.13.pom">
<sha256 value="068abfd585c50f3905dba88192b2f6525404aa8cd88781c2d5bf685bf217521e" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-bitflyer" version="4.4.2">
<artifact name="xchange-bitflyer-4.4.2.jar">
<sha256 value="5a68242ea812d6bdbc0cce087bf03c4977be5b78365dd66ab00bbea4e37e94d0" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitflyer-4.4.2.pom">
<sha256 value="9037c9ac214006c6103d049e6064f67f0e1a8fa91ca5f102c00fc1193f6b8b88" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-bitflyer" version="5.0.13">
<artifact name="xchange-bitflyer-5.0.13.jar">
<sha256 value="bb0a7693c3df777706d6c385decaa75a5864cc1ff29cb21f047387ece7a0bf73" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitflyer-5.0.13.pom">
<sha256 value="0794017671cb65cf7ec8ba25837f0bdca1030bc3c725803ed5b24a926e6c4008" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-bitstamp" version="4.4.2">
<artifact name="xchange-bitstamp-4.4.2.jar">
<sha256 value="8532a85d1a5a81f641e2598b7035944abb9167960ea885737daa29af2c019228" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitstamp-4.4.2.pom">
<sha256 value="ba4b4b32aa1bfe3c9f1021f6ea7757720769d40d2ad67733711bd52fd797e9c7" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-bitstamp" version="5.0.13">
<artifact name="xchange-bitstamp-5.0.13.jar">
<sha256 value="fa31554de4feee3859d472b2b4595c4525e7ab0cc808e8c46e203a654448fe63" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-bitstamp-5.0.13.pom">
<sha256 value="6e5d56a9c3d63c9fe877582ebc6735dbc1e90cee477eb512ac1d2acf21096158" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-btcmarkets" version="4.4.2">
<artifact name="xchange-btcmarkets-4.4.2.jar">
<sha256 value="43d48016368be58b847fd90c3022b7941b173da03251e3a82de275110c2e5829" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-btcmarkets-4.4.2.pom">
<sha256 value="529f836e8f30deb6fdadf3a492f2bfbd282f9cad27c9b05781cc1ab6cf084524" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-btcmarkets" version="5.0.13">
<artifact name="xchange-btcmarkets-5.0.13.jar">
<sha256 value="719c4257806a15416abaa1658e555a96305fec03fea01a10a2afc7d1fffcc87d" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-btcmarkets-5.0.13.pom">
<sha256 value="0cb79e637434bd7c16cf6e0128626e499248530c73c307aeba000230e98eab1b" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-cexio" version="4.4.2">
<artifact name="xchange-cexio-4.4.2.jar">
<sha256 value="c773726a025ecdd763ede8bde419deeef346a10cfb5da680af53ea55e33930b6" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-cexio-4.4.2.pom">
<sha256 value="eb743be06eb14584c1d89133eea79c6d65c25ef7241a524ccea62c33816c1f92" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-cexio" version="5.0.13">
<artifact name="xchange-cexio-5.0.13.jar">
<sha256 value="3aee69b41fb6b59fa8f56fff21b3913834eb6185ca440b60aa1a0711d46dd9d6" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-cexio-5.0.13.pom">
<sha256 value="a00fcbc26815dcfa126cb16c3491e22cd9fc88bf72643f721f36eed1cb5e0541" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.knowm.xchange" name="xchange-coinbasepro" version="5.0.13">
<artifact name="xchange-coinbasepro-5.0.13.jar">
<sha256 value="3972245632dad4f451921fd3b09fa87aacead3391720e3c82b14f1f850fdc108" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-coinbasepro-5.0.13.pom">
<sha256 value="cc3bd46e5363eff76d2cca01142a1a8228580b42af2197f091ad0413a296bd64" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-coinmarketcap" version="4.4.2">
<artifact name="xchange-coinmarketcap-4.4.2.jar">
<sha256 value="6a3d4a0e5493fd0e98f600974f26e393f377c7e9dff982a259e896a24e3191d9" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-coinmarketcap-4.4.2.pom">
<sha256 value="1d2cf8d872da7673118b700d118210c7cb95bb7b328608f751a41e5a18acfd53" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-coinmarketcap" version="5.0.13">
<artifact name="xchange-coinmarketcap-5.0.13.jar">
<sha256 value="fe9e2598e3d73e9922d54cecaed12be079013656e0bafebbd43aaf9e9d0273a5" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-coinmarketcap-5.0.13.pom">
<sha256 value="ebecfbee03311082b8594d33bd3735c49ba9514dfa41c6f891f196f17e06f9bf" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-coinmate" version="4.4.2">
<artifact name="xchange-coinmate-4.4.2.jar">
<sha256 value="a3616769a800f3137f00405e79ddd0f3ee2b107e140162598aa4262e5f71012f" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-coinmate-4.4.2.pom">
<sha256 value="cb6ba2974ee4701bd5c8b22f0dd7b6c1caa63c06b7e823e8b74ef9282abb6211" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-coinmate" version="5.0.13">
<artifact name="xchange-coinmate-5.0.13.jar">
<sha256 value="d1d6b10c0a58e04aab52b69722a6a15cb2e728ca39f80d5a2962bfc11ec4a333" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-coinmate-5.0.13.pom">
<sha256 value="7187897bed23eba066ecbd7765068ee7d4fee12cbdd6b2bdad3adc9fcffed326" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-coinone" version="4.4.2">
<artifact name="xchange-coinone-4.4.2.jar">
<sha256 value="9c31138d283f99f4be0a2434f8dc39b365dcb9f496e19492f8e279569778e986" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-coinone-4.4.2.pom">
<sha256 value="4f3c0a0cbe79b74aedc1f681fd16927bba84b65c25a27885d21c2712d00332b1" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-coinone" version="5.0.13">
<artifact name="xchange-coinone-5.0.13.jar">
<sha256 value="457b82bd59699cfb337967d7334357dff2531731d8e8521a67f233ee74768f83" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-coinone-5.0.13.pom">
<sha256 value="bb3beb2a22b3a8f8d4372ebe858d3ea2999a84e4279030ae11f254c4897d2f97" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-core" version="4.4.2">
<artifact name="xchange-core-4.4.2.jar">
<sha256 value="d4acbad92063a2e9f987364e0247e406f04de6f39116660b8166d3f26d38060f" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-core-4.4.2.pom">
<sha256 value="24d85987bb5251b0443bbb11f91a5cf32123ba352a635d92b341013d0be88c0f" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-core" version="5.0.13">
<artifact name="xchange-core-5.0.13.jar">
<sha256 value="e7fcf0c43adb4a156effd444ff8d3cdb6f17c55af4fa6cf1f0591ed35afd8184" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-core-5.0.13.pom">
<sha256 value="cf1971bd88eba00a0445e70f57574bf095045431b9a412184e53b3e8c2a4e9e7" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-exmo" version="4.4.2">
<artifact name="xchange-exmo-4.4.2.jar">
<sha256 value="6fa282673090d3883018b5224e2d14ee60b6afdaf693718aa67ca00d1a2fae55" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-exmo-4.4.2.pom">
<sha256 value="e1b329dd2402658198fe59814984621cfac7312e849081d71d499f177c6c5256" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-exmo" version="5.0.13">
<artifact name="xchange-exmo-5.0.13.jar">
<sha256 value="4414d2c68a67a7c1947e4940373ddda2ec4601b5d5fe976673895c1bee2485b5" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-exmo-5.0.13.pom">
<sha256 value="be4ff865ff579d0bb48d87904e0d3af6f6dd2cab3771bd343baff4739a1400d1" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-hitbtc" version="4.4.2">
<artifact name="xchange-hitbtc-4.4.2.jar">
<sha256 value="2dfb6912eab2fe50032ca292cc3c6eae89b4fd7d6b489b3095cc986ce5ef28d7" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-hitbtc-4.4.2.pom">
<sha256 value="3556a3cce231a4fe8f216e7b5891025d1412694b32c11cb3043550694e7cbefe" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-hitbtc" version="5.0.13">
<artifact name="xchange-hitbtc-5.0.13.jar">
<sha256 value="db86bd9a2bd1887252c7e4cdef97ba4b1d0139a2d0669793c25dbc42ee1eb7f9" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-hitbtc-5.0.13.pom">
<sha256 value="fb0ca258c46c9bca963f5f6bcb64f0f635695a91d285c4a72bd17463a643957a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-huobi" version="4.4.2">
<artifact name="xchange-huobi-4.4.2.jar">
<sha256 value="3835eceec9e3c6ecdf9de3850289bf731f5b2bb7bfad8beccfa81c86fc9a1505" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-huobi-4.4.2.pom">
<sha256 value="798221b9fac8913079f68d3fb2ec7b143f13db474ff6b5779b6e5391031cccd0" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-huobi" version="5.0.13">
<artifact name="xchange-huobi-5.0.13.jar">
<sha256 value="44bbe88e16adfaf65cb1df19d0729d28266f3d7e32363f95e4593a493cf21a38" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-huobi-5.0.13.pom">
<sha256 value="0ac71db129f9991d9c9e2eb489f885b8af4011ffcb02e53e1e4ea3307182918b" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-independentreserve" version="4.4.2">
<artifact name="xchange-independentreserve-4.4.2.jar">
<sha256 value="f0bbb3d039e9c04f877bace2b1230507b26e9b725e13412468c8876515666531" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-independentreserve-4.4.2.pom">
<sha256 value="f372436b14a529f1d5370c9fa14ca163e2db27fd3c3b81cbd5e0ab0a38e8203a" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-independentreserve" version="5.0.13">
<artifact name="xchange-independentreserve-5.0.13.jar">
<sha256 value="ffd5a054c2f7f238f143ce8ff803ee34b3bed5463776899eb9d9bda631dca165" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-independentreserve-5.0.13.pom">
<sha256 value="b4f874817c88e188ef1d2e9153c4457154840fa5a0c22eeee3699437b71cd02e" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-kraken" version="4.4.2">
<artifact name="xchange-kraken-4.4.2.jar">
<sha256 value="70098878fc66cb56fb00ade434e14bd5bcae6fbf94303465f39dede784e9ecd4" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-kraken-4.4.2.pom">
<sha256 value="6e80412700e2be7ac0f42d2c7499efe98f9989670c6dad752acd30045e84798d" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-kraken" version="5.0.13">
<artifact name="xchange-kraken-5.0.13.jar">
<sha256 value="3c8b152454f0a988186bce4b46e7fc83275e486fb9c511fdec8a0a5c9b80d910" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-kraken-5.0.13.pom">
<sha256 value="a9b0b79d3bc7ed6295b402cdc34367f1a965191db006eee7d473ad8ac421e8af" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-luno" version="4.4.2">
<artifact name="xchange-luno-4.4.2.jar">
<sha256 value="f8443f3d435beeca8e616dd071e634b5b5877802a6f2f6368eaf1dd2b526257e" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-luno-4.4.2.pom">
<sha256 value="6f2c61f889cd86d0a3507c0fb5bd80c1c1a47990b883c34766a99af47a30f5ba" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-luno" version="5.0.13">
<artifact name="xchange-luno-5.0.13.jar">
<sha256 value="b4b4b12a3c62f6991746db48dc6d601916becd8e2dbbb1faf906761c27f87a2a" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-luno-5.0.13.pom">
<sha256 value="60321a0d69e6a5d1e66101b4c270275001f58181d4378442713c2df0f030babc" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-mercadobitcoin" version="4.4.2">
<artifact name="xchange-mercadobitcoin-4.4.2.jar">
<sha256 value="89ba32a350cc294ad717f2d1bb7b5f289c5968cb43cdbf6e562bcc6a88483a98" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-mercadobitcoin-4.4.2.pom">
<sha256 value="fdd91c3b49cacdc07bef06d2228a372501c49f01558d9c9f4e8e5dde76343c07" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-mercadobitcoin" version="5.0.13">
<artifact name="xchange-mercadobitcoin-5.0.13.jar">
<sha256 value="c6cec9dce696d838f87a303bf227de8ba311a4614635aa70337b63545558fca3" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-mercadobitcoin-5.0.13.pom">
<sha256 value="ac6ee1ae7cb025168b92cd42a547acc74809f043d9efd509c88f0b8197b4430a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-parent" version="4.4.2">
<artifact name="xchange-parent-4.4.2.pom">
<sha256 value="d1e4f432d81a3e893d6079718db685e2d0dbe19956c28c8eeac4c3743337d118" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-parent" version="5.0.13">
<artifact name="xchange-parent-5.0.13.pom">
<sha256 value="5ddeb78e27d10ce803b22c305f6abd580a7435fe384eea7e343f966f1e265ff2" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-paribu" version="4.4.2">
<artifact name="xchange-paribu-4.4.2.jar">
<sha256 value="f48bca0dbed291c3109785f273666670a0e834e69b1c6c61a8f9ac684fbb7316" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-paribu-4.4.2.pom">
<sha256 value="be4150643b51905f2d1d97b5458d24e125323d29ef5f4ab290a049360139e275" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-paribu" version="5.0.13">
<artifact name="xchange-paribu-5.0.13.jar">
<sha256 value="b08a0cd45c4d42a841e665b4d563dbcabf57e680a9a19c3648448c5a02a6fd62" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-paribu-5.0.13.pom">
<sha256 value="7fc754f8385142dd1aacbb9bcb45461f9b5d54dee9abb498c79f90a1a225712a" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-poloniex" version="4.4.2">
<artifact name="xchange-poloniex-4.4.2.jar">
<sha256 value="19fc5d520c25b509f8a3deed54dc5294e33ed8db7026e90552267d567b8c1ecf" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-poloniex-4.4.2.pom">
<sha256 value="b526186d2ea6067d53aeb166f132eafbbd0977506b9381db203d13f35922667d" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-poloniex" version="5.0.13">
<artifact name="xchange-poloniex-5.0.13.jar">
<sha256 value="d2148a2ad3fdca6cc7e0529b7a8217e900dd296e56844485702c58cb13802ebc" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-poloniex-5.0.13.pom">
<sha256 value="2dadc019ac83d23b7d8d452c5ddca3f3463c1a71be645a06d8a6aa771e2b2380" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.knowm.xchange" name="xchange-quoine" version="4.4.2">
<artifact name="xchange-quoine-4.4.2.jar">
<sha256 value="59afe7ad35d55a4690cdabf0a15e1250455ee52bea4eb7c5889a63752a7e4c90" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-quoine-4.4.2.pom">
<sha256 value="d3f791725b7f18867b35c0addbca94883d2bbb6a645cc46d2226d1eca5f22034" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade XChange 5.0.13, remove BitBay CoinPaprika add CoinbasePro. Co-Authored-by: jmacxx <47253594+jmacxx@users.noreply.github.com>
2022-05-31 02:38:28 +00:00
<component group="org.knowm.xchange" name="xchange-quoine" version="5.0.13">
<artifact name="xchange-quoine-5.0.13.jar">
<sha256 value="efebc2c85c31961b213981720053d58770b712201c3297011ad8d7c3562a2480" origin="Generated by Gradle"/>
</artifact>
<artifact name="xchange-quoine-5.0.13.pom">
<sha256 value="86affbb1a52a897c8af6d748ca4e29117bf8f46fef93a1f6ce8b45a64e1e1fe4" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.mockito" name="mockito-core" version="3.5.15">
<artifact name="mockito-core-3.5.15.jar">
<sha256 value="f2c9c7080ada5640d28d01fc29d814438dd143e5331f76ef6908dcdd3ec141f0" origin="Generated by Gradle"/>
</artifact>
deps: update tor to 0.4.5.10 (netlayer 0.7.2) https://github.com/bisq-network/netlayer/releases/tag/0.7.2
2022-03-13 09:41:01 +00:00
<artifact name="mockito-core-3.5.15.pom">
<sha256 value="c622ea8d161e69ff8e578d0654043c18e3b1cf54f98b340532a85a6eb97d4381" origin="Generated by Gradle"/>
</artifact>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.mockito" name="mockito-core" version="4.0.0">
<artifact name="mockito-core-4.0.0.jar">
<sha256 value="904634ccb32c1d912e528e964a5066dd5992163b064b0e7207bc35d3734d108d" origin="Generated by Gradle"/>
</artifact>
<artifact name="mockito-core-4.0.0.pom">
<sha256 value="9146f147483ae9dfdb226eb928e81926122fadc1665648262e6e095d15762ebf" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.mockito" name="mockito-core" version="5.2.0">
<artifact name="mockito-core-5.2.0.jar">
<sha256 value="46e3f8dacd8ec62c8aa6fb11f8867624fb44a03e97fdfc628609346d5dc7e159" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.objenesis" name="objenesis" version="3.1">
<artifact name="objenesis-3.1.jar">
<sha256 value="cdb3d038c188de6f46ffd5cd930be2d5e5dba59c53b26437995d534e3db2fb80" origin="Generated by Gradle"/>
</artifact>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<artifact name="objenesis-3.1.pom">
<sha256 value="d46072a46dff7707e06545777486b18d73e052231e3139cd3d9c3f347bc4e6e4" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.objenesis" name="objenesis" version="3.2">
<artifact name="objenesis-3.2.jar">
<sha256 value="03d960bd5aef03c653eb000413ada15eb77cdd2b8e4448886edf5692805e35f3" origin="Generated by Gradle"/>
</artifact>
<artifact name="objenesis-3.2.pom">
<sha256 value="4e10adf1477b8c711b45b8a15eb960f6b44871f5e1def38f16681348aa166b0c" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.objenesis" name="objenesis" version="3.3">
<artifact name="objenesis-3.3.jar">
<sha256 value="02dfd0b0439a5591e35b708ed2f5474eb0948f53abf74637e959b8e4ef69bfeb" origin="Generated by Gradle"/>
</artifact>
</component>
deps: update to netlayer 0.7.3 Co-authored-by: chimp1984 <chimp1984@gmx.com>
2022-06-22 09:15:22 +00:00
<component group="org.objenesis" name="objenesis-parent" version="3.1">
<artifact name="objenesis-parent-3.1.pom">
<sha256 value="1493584824e110e22d6047584978ca2fc9907987102369bdb1e3773d54963ada" origin="Generated by Gradle"/>
</artifact>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.objenesis" name="objenesis-parent" version="3.2">
<artifact name="objenesis-parent-3.2.pom">
<sha256 value="0859ba0d5cfeefb13964e5862c036faa48a0bccff4932638fb13fe3445df33f7" origin="Generated by Gradle"/>
</artifact>
</component>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<component group="org.openjfx" name="javafx" version="16">
<artifact name="javafx-16.pom">
<sha256 value="18d9784212d04475bfe4a5f4038e0fc78146f9a721eb6b9a52955d3b4b20d3ca" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<component group="org.openjfx" name="javafx-base" version="16">
<artifact name="javafx-base-16-linux.jar">
<sha256 value="b825e220d685ecbd77e76f2cd52793132e6c9a10e23ee3361673cb29033413c0" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-base-16-mac.jar">
<sha256 value="8cb4a023706d392d0a733aaee41be839e8418448ab0090a8115a9b909d595c77" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-base-16-win.jar">
<sha256 value="23abcdffb6f92d8b37531080682034d01c177f1229118a2f7646331c51c6ed63" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-base-16.jar">
<sha256 value="036955291b3633b6e11106df315f7a561218d31dcb4280078fe4d2414925f557" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-base-16.pom">
<sha256 value="09fe0f2eda8b6f3d4c55b28e32b6b7b2782847add96a686d3048753baa781901" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<component group="org.openjfx" name="javafx-controls" version="16">
<artifact name="javafx-controls-16-linux.jar">
<sha256 value="fd0aba38a0dde9836845c6d671501f4c30e6cff6f2d72748f75742dbcfc74df9" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-controls-16-mac.jar">
<sha256 value="4add6fdf120ab9c784dc6e700c158d411d9371aaba7bbb61ad9f9d016f2cce44" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-controls-16-win.jar">
<sha256 value="a7f6e4757163c38a5e6cf26b426e9daf788ad1b57513111d362b3bbbc298d13b" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-controls-16.jar">
<sha256 value="dfdbe63f9717b2cd84c9fd34b28a8ddffdbe25cc1e4c2ff9f171f07ca725e0f4" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<component group="org.openjfx" name="javafx-fxml" version="16">
<artifact name="javafx-fxml-16-linux.jar">
<sha256 value="65249a5a47357283f21c5fa85b2e91255f7e5b0b86a2ec3dd2cc220541d7ae0b" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-fxml-16-mac.jar">
<sha256 value="b722e590930180ff7c43d34281202251e1fe8d1f81b16098cda78600780b7f46" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-fxml-16-win.jar">
<sha256 value="e8313ffb783c26acbbc1267448bbfdf2f05126e5845a06c6f29a43db7483606d" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<component group="org.openjfx" name="javafx-graphics" version="16">
<artifact name="javafx-graphics-16-linux.jar">
<sha256 value="a2f5e1ea5aeb3ae57e63a1c853a4edf1e38b6f2fe76997ab864ad8b3c54bed53" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-graphics-16-mac.jar">
<sha256 value="23a67ad877f283039a20dd827f68988c1f952fe4958d039c006762883f1f04ab" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-graphics-16-win.jar">
<sha256 value="78124668c64db443cf3e105b9c2f6d7061e7c72ad5ad2de63a13adc46ef2ca8c" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-graphics-16.jar">
<sha256 value="77533b2922a853a3e1350c8e6650f6cf746000d20efef69119c6324086883b95" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-graphics-16.pom">
<sha256 value="b8fb99688eccae62be724bd72b34dfff1f8e1cddbe44649f5ef9a082e520c47e" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<component group="org.openjfx" name="javafx-swing" version="16">
<artifact name="javafx-swing-16-linux.jar">
<sha256 value="ffb495dbbf314f56784828b91ee2cc304bd891b862b79fdd7f3338e6cffd74f7" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-swing-16-mac.jar">
<sha256 value="6b49d1754f9c987b48244c8c9612214f05229a67b7bd43f4ba98f76b4617ae56" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
update to jfx 16 to fix segfault in legacy ui
2022-10-24 14:00:22 +00:00
<artifact name="javafx-swing-16-win.jar">
<sha256 value="5244ee1fe470507cebeaf1111937168556163a0b90e6bf9bba5c16b4c3280012" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
<component group="org.opentest4j" name="opentest4j" version="1.2.0">
<artifact name="opentest4j-1.2.0.jar">
<sha256 value="58812de60898d976fb81ef3b62da05c6604c18fd4a249f5044282479fc286af2" origin="Generated by Gradle"/>
</artifact>
<artifact name="opentest4j-1.2.0.pom">
<sha256 value="a96e671816c1ff8803bdec74c9241f025bdfb277da5d2b4ee02266405936f994" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.ow2" name="ow2" version="1.5">
<artifact name="ow2-1.5.pom">
<sha256 value="0f8a1b116e760b8fe6389c51b84e4b07a70fc11082d4f936e453b583dd50b43b" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.ow2.asm" name="asm" version="9.4">
<artifact name="asm-9.4.jar">
<sha256 value="39d0e2b3dc45af65a09b097945750a94a126e052e124f93468443a1d0e15f381" origin="Generated by Gradle"/>
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="org.ow2.asm" name="asm" version="9.5">
<artifact name="asm-9.5.jar">
<sha256 value="b62e84b5980729751b0458c534cf1366f727542bb8d158621335682a460f0353" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
</component>
<component group="org.ow2.asm" name="asm-commons" version="9.4">
<artifact name="asm-commons-9.4.jar">
<sha256 value="0c128a9ec3f33c98959272f6d16cf14247b508f58951574bcdbd2b56d6326364" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="org.ow2.asm" name="asm-commons" version="9.5">
<artifact name="asm-commons-9.5.jar">
<sha256 value="72eee9fbafb9de8d9463f20dd584a48ceeb7e5152ad4c987bfbe17dd4811c9ae" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
</component>
<component group="org.ow2.asm" name="asm-tree" version="9.4">
<artifact name="asm-tree-9.4.jar">
<sha256 value="c42d479cf24566a21eb20af7eeaeef4e86bdb4a886306cf72f483b65e75b2acf" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
Aggregate and send coverage report to Codacy
2023-05-10 22:47:12 +00:00
<component group="org.ow2.asm" name="asm-tree" version="9.5">
<artifact name="asm-tree-9.5.jar">
<sha256 value="3c33a648191079aeaeaeb7c19a49b153952f9e40fe86fbac5205554ddd9acd94" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.pcollections" name="pcollections" version="2.1.2">
<artifact name="pcollections-2.1.2.jar">
<sha256 value="29c8ffcc5c6a97f059941148593ad00fe2cdf78af1d88d46bcf0d1bb703606c2" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.projectlombok" name="lombok" version="1.18.12">
<artifact name="lombok-1.18.12.jar">
<sha256 value="49381508ecb02b3c173368436ef71b24c0d4418ad260e6cc98becbcf4b345406" origin="Generated by Gradle"/>
</artifact>
<artifact name="lombok-1.18.12.pom">
<sha256 value="bca2bb252c6ec5db92584af7ab26f787b14a155f587c3e30ec1e1da0d4164694" origin="Generated by Gradle"/>
</artifact>
</component>
update lombok to fix eclipse refactor > rename issue
2022-05-14 18:47:36 +00:00
<component group="org.projectlombok" name="lombok" version="1.18.24">
<artifact name="lombok-1.18.24.jar">
<sha256 value="d3584bc2db03f059f984fb0a9c119aac1fa0da578a448e69fc3f68b36584c749" origin="Generated by Gradle"/>
</artifact>
<artifact name="lombok-1.18.24.pom">
<sha256 value="2ab23568c9a823eb7a9d1171abbe5e2d2c6872e1a2db6878ef030c6d5ca47710" origin="Generated by Gradle"/>
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="org.reflections" name="reflections" version="0.10.2">
<artifact name="reflections-0.10.2.jar">
<sha256 value="938a2d08fe54050d7610b944d8ddc3a09355710d9e6be0aac838dbc04e9a2825" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.slf4j" name="jcl-over-slf4j" version="1.7.25">
<artifact name="jcl-over-slf4j-1.7.25.jar">
<sha256 value="5e938457e79efcbfb3ab64bc29c43ec6c3b95fffcda3c155f4a86cc320c11e14" origin="Generated by Gradle"/>
</artifact>
<artifact name="jcl-over-slf4j-1.7.25.pom">
<sha256 value="f318976d3d4bd3f36a9bab47af4b17eaf671603e3d7a92e6c67b2004462e0f2d" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.slf4j" name="jul-to-slf4j" version="1.7.25">
<artifact name="jul-to-slf4j-1.7.25.jar">
<sha256 value="416c5a0c145ad19526e108d44b6bf77b75412d47982cce6ce8d43abdbdbb0fac" origin="Generated by Gradle"/>
</artifact>
<artifact name="jul-to-slf4j-1.7.25.pom">
<sha256 value="b30fcd17b18557a188dfa1148afb56dec3f4386dbdad6c7fbf15667e22f665df" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.slf4j" name="jul-to-slf4j" version="1.7.33">
<artifact name="jul-to-slf4j-1.7.33.jar">
<sha256 value="e8c2fa1ecf1a1828878909e026cba19325bb39896a58fe2e09c59fad69e9dae9" origin="Generated by Gradle"/>
</artifact>
<artifact name="jul-to-slf4j-1.7.33.pom">
<sha256 value="676fbb091f72e98ee0a2fbf6180f0b82ed9ebb1a62be36b87ac813139247ac41" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.slf4j" name="log4j-over-slf4j" version="1.7.25">
<artifact name="log4j-over-slf4j-1.7.25.jar">
<sha256 value="c84c5ce4bbb661369ccd4c7b99682027598a0fb2e3d63a84259dbe5c0bf1f949" origin="Generated by Gradle"/>
</artifact>
<artifact name="log4j-over-slf4j-1.7.25.pom">
<sha256 value="ab5d6007f23e131b151873de8ca10e34674e3cb63facd11464ece43de99b2e02" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.slf4j" name="slf4j-api" version="1.7.22">
<artifact name="slf4j-api-1.7.22.jar">
<sha256 value="3a4cd4969015f3beb4b5b4d81dbafc01765fb60b8a439955ca64d8476fef553e" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.slf4j" name="slf4j-api" version="1.7.25">
<artifact name="slf4j-api-1.7.25.jar">
<sha256 value="18c4a0095d5c1da6b817592e767bb23d29dd2f560ad74df75ff3961dbde25b79" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.slf4j" name="slf4j-api" version="1.7.30">
<artifact name="slf4j-api-1.7.30.jar">
<sha256 value="cdba07964d1bb40a0761485c6b1e8c2f8fd9eb1d19c53928ac0d7f9510105c57" origin="Generated by Gradle"/>
</artifact>
</component>
update to monero-java v0.7.13 remove old dependencies from verification-metadata.xml
2023-04-02 21:06:59 +00:00
<component group="org.slf4j" name="slf4j-api" version="1.7.36">
<artifact name="slf4j-api-1.7.36.jar">
<sha256 value="d3ef575e3e4979678dc01bf1dcce51021493b4d11fb7f1be8ad982877c16a1c0" origin="Generated by Gradle"/>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.slf4j" name="slf4j-parent" version="1.7.25">
<artifact name="slf4j-parent-1.7.25.pom">
<sha256 value="18f5c52120db036e88d6136f8839c832d074bdda95c756c6f429249d2db54ac6" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.slf4j" name="slf4j-parent" version="1.7.33">
<artifact name="slf4j-parent-1.7.33.pom">
<sha256 value="7da72f04110b30ac1deea7d2d64d69499930dc07813cb686d1e2ee8cced667d0" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.sonatype.oss" name="oss-parent" version="7">
<artifact name="oss-parent-7.pom">
<sha256 value="b51f8867c92b6a722499557fc3a1fdea77bdf9ef574722fe90ce436a29559454" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.sonatype.oss" name="oss-parent" version="9">
<artifact name="oss-parent-9.pom">
<sha256 value="fb40265f982548212ff82e362e59732b2187ec6f0d80182885c14ef1f982827a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework" name="spring-aop" version="4.3.14.RELEASE">
<artifact name="spring-aop-4.3.14.RELEASE.jar">
<sha256 value="045bd5b0e8f5567432b4a2228ac5a1b0f5d9b62b393e352a99ae025ff6ab1e12" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-aop-4.3.14.RELEASE.pom">
<sha256 value="feadd2a533a5013b23eadba846fdc9c9961d580cfb4236d51f49e91aaf874dbb" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-aop" version="5.3.15">
<artifact name="spring-aop-5.3.15.jar">
<sha256 value="58cf948758d31e2ac8636dfa27cd4211a7a89e54e16f7318c0ec3f964c83b2b7" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-aop-5.3.15.pom">
<sha256 value="4dadfefd863348b5af002c8a68b1dd6d9f80e0465dea44429041cba68feb886c" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework" name="spring-beans" version="4.3.14.RELEASE">
<artifact name="spring-beans-4.3.14.RELEASE.jar">
<sha256 value="62ba63c30d30a221b69ce77d5d626554af1d61dc736cebd45ba7c688ee1048ab" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-beans-4.3.14.RELEASE.pom">
<sha256 value="ae2f90dba31e8ec9b2896afed10b2ea216f2775f94b4efe6faa8da3420b81976" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-beans" version="5.3.15">
<artifact name="spring-beans-5.3.15.jar">
<sha256 value="f4facec88ada2e86be062f90b3f1d39fd6660de7ecc2dc45afc45fb31e9699b2" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-beans-5.3.15.pom">
<sha256 value="2229926331e98a89d3b1c04ac465aa96cc7a1e05608176971a8435d9c09e139d" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework" name="spring-context" version="4.3.14.RELEASE">
<artifact name="spring-context-4.3.14.RELEASE.jar">
<sha256 value="532eefed557776476cdc19bed3ff773fb9335dd064fdd4b05d5cbff843cffdb4" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-context-4.3.14.RELEASE.pom">
<sha256 value="7757ae5afd1e113d094a2ca37a4e83ff3f500d60be9c9c225e38c8ff1664ac0f" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-context" version="5.3.15">
<artifact name="spring-context-5.3.15.jar">
<sha256 value="b23c4e897e846750d6409982c077f237074534df51eae0e2c589c9783950bf7b" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-context-5.3.15.pom">
<sha256 value="455e3dfe81dcd4381e1b64277e06e969f052c6752a7a915bba917a494eda82e7" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework" name="spring-core" version="4.3.14.RELEASE">
<artifact name="spring-core-4.3.14.RELEASE.jar">
<sha256 value="461e35d0dd65e7dedcc9ce5dfc88692768d02216c33d9abe9cac50b5671e1480" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-core-4.3.14.RELEASE.pom">
<sha256 value="b6919ef5b3f29b82d584be03b73dcfa8a626f9c229c785962db979ed79796e66" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-core" version="5.3.15">
<artifact name="spring-core-5.3.15.jar">
<sha256 value="cf3cb24e0f051e338159ad4a60e156d34b082422a80ece3f045bbc6e8c6246ea" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-core-5.3.15.pom">
<sha256 value="3fc50bf76d4c0fffb95236f95d7009d36db494190fe6684badd42bfecc4040b9" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework" name="spring-expression" version="4.3.14.RELEASE">
<artifact name="spring-expression-4.3.14.RELEASE.jar">
<sha256 value="932e0e19bd9838aa3f10ea5be8e4fc90c1a2dc13af6ec389a1bd6ef1a213f7d7" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-expression-4.3.14.RELEASE.pom">
<sha256 value="a19aa551f8c9b8ccf90650745eba5eef63b8f845ad594a3bf654cb6b75b8960e" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-expression" version="5.3.15">
<artifact name="spring-expression-5.3.15.jar">
<sha256 value="f2e7151c690b9fe6e640d3253361a6953fa49ef9b86679efe97274674ded2226" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-expression-5.3.15.pom">
<sha256 value="e2179e3e5346d1b093d4b0bf8356e445e6252de1cea903977f96bcd104397294" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework" name="spring-framework-bom" version="4.3.14.RELEASE">
<artifact name="spring-framework-bom-4.3.14.RELEASE.pom">
<sha256 value="3bb35a75ac3723622bbe1c134595697665384ad3c27c5831619ffa78deec0f20" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-framework-bom" version="5.3.15">
<artifact name="spring-framework-bom-5.3.15.pom">
<sha256 value="eda6cbdee12aa6f80c3d5bc770d9dfc71db9c99b603d1c6f91686946b2b2608b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework" name="spring-jcl" version="5.3.15">
<artifact name="spring-jcl-5.3.15.jar">
<sha256 value="504afd1b05616160ddeecd57537864fd96abd5067f952071c4c8e1246338d123" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-jcl-5.3.15.pom">
<sha256 value="65e3c591eb9378152d1625eda67e710073815618d767446b9bc3a781a4bbeda0" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework" name="spring-web" version="4.3.14.RELEASE">
<artifact name="spring-web-4.3.14.RELEASE.jar">
<sha256 value="083e47f516ccded21ee4b79044c5842f23049f38bec936f4f25b6927f08984a7" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-web-4.3.14.RELEASE.pom">
<sha256 value="07f3fb858e737b68e2c673e793dcd10523d153359bc66009c029c4cdb67cca5b" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-web" version="5.3.15">
<artifact name="spring-web-5.3.15.jar">
<sha256 value="4c11dbe95c40703d6e55a72c5a1f884f4ffd2b4eb72f8d9cfa3912827aa9f215" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-web-5.3.15.pom">
<sha256 value="301725d9a09f05d7f9c0063c6b1000579137894447ee3c1159800e2c4d0d1c59" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework" name="spring-webmvc" version="4.3.14.RELEASE">
<artifact name="spring-webmvc-4.3.14.RELEASE.jar">
<sha256 value="01f4eceae4568feb4776b78554e72774480fe52f28d2d64d777796be6e1f4dfc" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-webmvc-4.3.14.RELEASE.pom">
<sha256 value="b6efbbaabf9ec3cdf63fead5d6b7e121b932b38d3a5e6064af42818887c5bba3" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework" name="spring-webmvc" version="5.3.15">
<artifact name="spring-webmvc-5.3.15.jar">
<sha256 value="77ee2f3d7ff5eef47e15937033de6c478c84bb40a3b90405645f03780dcd9fe1" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-webmvc-5.3.15.pom">
<sha256 value="a110d5d3f696b3c4e8298bf49b8b1e01bb5b84fd99ffec2953600e87bd61eca1" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot" version="1.5.10.RELEASE">
<artifact name="spring-boot-1.5.10.RELEASE.jar">
<sha256 value="b80cbef3006fddb3b6981fb5238bdabf42dbebf3b7293996420c52922fcb03f3" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-1.5.10.RELEASE.pom">
<sha256 value="a910327d7b138094f70b3366d84d658a2cc5daeff943ba664f810111fcbf7ee0" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot" version="2.6.3">
<artifact name="spring-boot-2.6.3.jar">
<sha256 value="33781652e93968fb9b7c6c0856018f42de6aa212b6abce3e3bbc1840c195446f" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-2.6.3.pom">
<sha256 value="cde23eea5a59c8294d15cf3822abc2d5b58c85f1a0899f3641cc512be10f65bb" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-actuator" version="1.5.10.RELEASE">
<artifact name="spring-boot-actuator-1.5.10.RELEASE.jar">
<sha256 value="aeac7c1394577a28f42ccfb886f9081a5d191b292f0c4530d472cfe847005321" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-actuator-1.5.10.RELEASE.pom">
<sha256 value="05202b33f7b7af3dd3250e71dd50da043b17da321213e1b5b12587213c7fd6e3" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework.boot" name="spring-boot-autoconfigure" version="1.5.10.RELEASE">
<artifact name="spring-boot-autoconfigure-1.5.10.RELEASE.jar">
<sha256 value="fe31c8fffef0c8e78212386bdc9c45efba9ca510f9091b59fddd0c73f29274f1" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-autoconfigure-1.5.10.RELEASE.pom">
<sha256 value="b5287acaac84aded5d5a378363baafad10f5306d2c9c9e3d2d20a7f1908b4b52" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-autoconfigure" version="2.6.3">
<artifact name="spring-boot-autoconfigure-2.6.3.jar">
<sha256 value="22448c1afe9f72e79c1c640c2c62143f51a1a9d770e41a1ff9f744d15184f099" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-autoconfigure-2.6.3.pom">
<sha256 value="a25102e9d90c5c0e33e2304aa0b899e5c7d65fc20bb8c162f1d85ffc67c2ddbc" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework.boot" name="spring-boot-buildpack-platform" version="2.6.3">
<artifact name="spring-boot-buildpack-platform-2.6.3.jar">
<sha256 value="34aea693bb4c84a7eee6051a14a9a12374a21dc26b4413570bd30363ec976ebc" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-dependencies" version="1.5.10.RELEASE">
<artifact name="spring-boot-dependencies-1.5.10.RELEASE.pom">
<sha256 value="aa82386c27e7548624edcc4812ab7115aa9cec15d6716ab4280f3a79791554b3" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-dependencies" version="2.6.3">
<artifact name="spring-boot-dependencies-2.6.3.pom">
<sha256 value="efae8b2c6051e3b7c9cfc953139eb5142f8c5c3af5c75178b7eaa793e7f2d5ca" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-gradle-plugin" version="1.5.10.RELEASE">
<artifact name="spring-boot-gradle-plugin-1.5.10.RELEASE.jar">
<sha256 value="f430e1db7b8746c6feeee5cc8b5ff664e0fae3b760983d0a35d71642997f974d" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-gradle-plugin" version="2.6.3">
<artifact name="spring-boot-gradle-plugin-2.6.3.jar">
<sha256 value="98c3ea15d56e9d76b2a4b2672771251752beb0aa5a89991f6b5227e51b665262" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-loader-tools" version="1.5.10.RELEASE">
<artifact name="spring-boot-loader-tools-1.5.10.RELEASE.jar">
<sha256 value="32ac263748bbc6a128c732402579f26849b37d62e0ef4c457c34dfceea0bfc71" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-loader-tools" version="2.6.3">
<artifact name="spring-boot-loader-tools-2.6.3.jar">
<sha256 value="28246505aea783cc7ea279a91200803e53d0a37b27854fe498d3bdfa0c71a623" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-parent" version="1.5.10.RELEASE">
<artifact name="spring-boot-parent-1.5.10.RELEASE.pom">
<sha256 value="2eb05ff3c2c52ce028248e0f04b83456e16bbac108015fdc4465e91eb77bb539" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework.boot" name="spring-boot-starter" version="1.5.10.RELEASE">
<artifact name="spring-boot-starter-1.5.10.RELEASE.jar">
<sha256 value="227664ae2a19e5e20f4acb6ca8a7c233c4af6f5900ee048187568de3d610a369" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-1.5.10.RELEASE.pom">
<sha256 value="fa75488dd765f65d3b88179f220ca436354d1c43d5482d649e01e2d41f5c5ac3" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-starter" version="2.6.3">
<artifact name="spring-boot-starter-2.6.3.jar">
<sha256 value="9ca85294d820219cacd577fbf208d970a1e2dfa3f63da84c84dca1c6d5da5fdb" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-2.6.3.pom">
<sha256 value="a00fdba627fcb205639f2554815739bf7ba57d53f6f5f19a2f2d1b30b8680a47" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-actuator" version="1.5.10.RELEASE">
<artifact name="spring-boot-starter-actuator-1.5.10.RELEASE.jar">
<sha256 value="359123474402f4b134c94bf031719f37499ab27cf9b82bfe75108fe472b8acb9" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-actuator-1.5.10.RELEASE.pom">
<sha256 value="18467101713eea1af31086692894c5124d2a1385d24013706a79262fd76ff270" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-json" version="2.6.3">
<artifact name="spring-boot-starter-json-2.6.3.jar">
<sha256 value="693d423f4e3a87cad4033b90c8fcda3dd4aafe3fd2c57b26d7f4b1cd2efc691f" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-json-2.6.3.pom">
<sha256 value="d7ef3ccd34ab8a54bf5936bb4826d721445cf4fcd1623a1409b9373cb5329182" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-logging" version="1.5.10.RELEASE">
<artifact name="spring-boot-starter-logging-1.5.10.RELEASE.jar">
<sha256 value="93491699f13ee1e2e439c962ecaa65b9103d9e9ddf79ceb7644c39507c2e4b26" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-logging-1.5.10.RELEASE.pom">
<sha256 value="3e41061d53066ffea4215bc862448bee4d489fee1ba23d294f835a4b53b220c0" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-logging" version="2.6.3">
<artifact name="spring-boot-starter-logging-2.6.3.jar">
<sha256 value="9aa962966d9b080cccf23be999479bad183e8a3e83ac1f82760e484ef3e4391f" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-logging-2.6.3.pom">
<sha256 value="90179cb048e00199302da323c4892ffd5fd1018ca34490472b436e7d6d52fc6f" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-parent" version="1.5.10.RELEASE">
<artifact name="spring-boot-starter-parent-1.5.10.RELEASE.pom">
<sha256 value="5cd426a3893f72f40d2145fa3da5012be3f75ea0e69fdae545bc100e5270497b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework.boot" name="spring-boot-starter-tomcat" version="1.5.10.RELEASE">
<artifact name="spring-boot-starter-tomcat-1.5.10.RELEASE.jar">
<sha256 value="a835ebb62173c031d75651647137d3efd9172c3688e476d553e0bb95917d9cbc" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-tomcat-1.5.10.RELEASE.pom">
<sha256 value="83acff5c46ae35224a1b55d0b8a1d8d6c568a43bc27dbb8f3cdb3fb3d8679bc4" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-tomcat" version="2.6.3">
<artifact name="spring-boot-starter-tomcat-2.6.3.jar">
<sha256 value="51cec9c434070da9a9681d8eb251e40cd4572eec5cebb66fb72adbc0ea291d96" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-tomcat-2.6.3.pom">
<sha256 value="7c2853e9c910c10b9232e5fe37640a24ea86f4f61d08030c1ce0c3676b4355d7" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-web" version="1.5.10.RELEASE">
<artifact name="spring-boot-starter-web-1.5.10.RELEASE.jar">
<sha256 value="8e7cde2cb4c7fb70ff398264b65088500e06107247594c9a5f1d0f0b608793e6" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-web-1.5.10.RELEASE.pom">
<sha256 value="d8defe579f5cea5ae2f01ddfb7c72ff2fbbb9192abaec41ea236fdb33a507643" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.boot" name="spring-boot-starter-web" version="2.5.6">
<artifact name="spring-boot-starter-web-2.5.6.jar">
<sha256 value="2374266336e8852144b0cb7bd149509535bf5dbc6b66b896d5a185d55bb22b5e" origin="Generated by Gradle"/>
</artifact>
<artifact name="spring-boot-starter-web-2.5.6.pom">
<sha256 value="5ecf1ddd974ea71c42ef355f1908a07baff1a9ccad560fb7b517ad1b591184a2" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.boot" name="spring-boot-starters" version="1.5.10.RELEASE">
<artifact name="spring-boot-starters-1.5.10.RELEASE.pom">
<sha256 value="5c8e342189284e54799aa3ddadff977abaa4039e4fab60822951b6a7af5f1e77" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.data" name="spring-data-bom" version="2021.1.1">
<artifact name="spring-data-bom-2021.1.1.pom">
<sha256 value="aaeb3b5655f07c941a754831f91faca57490940c7623a35b4b5007e554a7cff2" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.data" name="spring-data-releasetrain" version="Ingalls-SR10">
<artifact name="spring-data-releasetrain-Ingalls-SR10.pom">
<sha256 value="c2134ef9e68da1969002d0e68a22801f096f393c255e99662a4145dc217f134e" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework.data.build" name="spring-data-build" version="1.9.10.RELEASE">
<artifact name="spring-data-build-1.9.10.RELEASE.pom">
<sha256 value="284ed757469a0e11395067dd42f6ad6761bbae0a6d192a5188282a1b6e3857ef" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework.integration" name="spring-integration-bom" version="4.3.14.RELEASE">
<artifact name="spring-integration-bom-4.3.14.RELEASE.pom">
<sha256 value="99072cdcd131b9c43109482d9806bde1e0380cfceb919acd79c4c420083e7ba9" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.integration" name="spring-integration-bom" version="5.5.8">
<artifact name="spring-integration-bom-5.5.8.pom">
<sha256 value="ba5a69710b68f2987cfca34b0ff1939043e15c13f4ed1af1a7173add00129986" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.springframework.security" name="spring-security-bom" version="4.2.4.RELEASE">
<artifact name="spring-security-bom-4.2.4.RELEASE.pom">
<sha256 value="1d00dfa7a1804ce9875fb8f6c6b29293f05e4f56a020baf164fdc1187239ce77" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.springframework.security" name="spring-security-bom" version="5.6.1">
<artifact name="spring-security-bom-5.6.1.pom">
<sha256 value="017da208dddb91b857b66ad22dc45184c6509323ef29cc8312f8747349dac401" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.springframework.session" name="spring-session-bom" version="2021.1.1">
<artifact name="spring-session-bom-2021.1.1.pom">
<sha256 value="999e7f5c223e42341fd0561921f1664e03f7fa3e0e1dcafbbd4664813e81abb9" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.threeten" name="threetenbp" version="1.3.3">
<artifact name="threetenbp-1.3.3.jar">
<sha256 value="7bbee842b0334f63627556d3c657aab82431f3a207c8dc4dcfc379d7d210a8c6" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.tomlj" name="tomlj" version="1.0.0">
<artifact name="tomlj-1.0.0.jar">
<sha256 value="32697c7567b2921c473678a820b13fc64700aa87bb14576eeb48d0ed5847cfd4" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.tukaani" name="xz" version="1.6">
<artifact name="xz-1.6.jar">
<sha256 value="a594643d73cc01928cf6ca5ce100e094ea9d73af760a5d4fb6b75fa673ecec96" origin="Generated by Gradle"/>
</artifact>
<artifact name="xz-1.6.pom">
<sha256 value="06843f984cf0ad3ecd4196861404ddc4af83ec37a1eb7a1773ab89db02b4020f" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to gradle 8.0.2 for checkstyle heap size adjustment
2023-03-21 11:07:39 +00:00
<component group="org.vafer" name="jdependency" version="2.8.0">
<artifact name="jdependency-2.8.0.jar">
<sha256 value="bfd2cc7e1bfc78aa83b44c0a54bf2cde38a4382ec24728af683d98dc6be78192" origin="Generated by Gradle"/>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
</artifact>
</component>
Removing star and unused imports with checkstyle
2023-03-14 19:28:47 +00:00
<component group="org.xmlresolver" name="xmlresolver" version="4.6.0">
<artifact name="xmlresolver-4.6.0-data.jar">
<sha256 value="6865c34f535d339bc549c50e7e411884fba3b54896a441b6cf4c2426baa7fe06" origin="Generated by Gradle"/>
</artifact>
<artifact name="xmlresolver-4.6.0.jar">
<sha256 value="b8b0296855d27685329b4c92f54201a0ba5e15746a96c256c3faf85bf836f1a6" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.yaml" name="snakeyaml" version="1.17">
<artifact name="snakeyaml-1.17.jar">
<sha256 value="5666b36f9db46f06dd5a19d73bbff3b588d5969c0f4b8848fde0f5ec849430a5" origin="Generated by Gradle"/>
</artifact>
<artifact name="snakeyaml-1.17.pom">
<sha256 value="dac6da64d27afbf4170721867104cb07789118c47d6238572cff45d6698d31b7" origin="Generated by Gradle"/>
</artifact>
</component>
upgrade to Gradle 7.3.3 (#439) * upgrade to Gradle 7.3.3 * add verification hashes for mac and windows * add verification hash for windows
2022-09-19 12:59:57 +00:00
<component group="org.yaml" name="snakeyaml" version="1.29">
<artifact name="snakeyaml-1.29.jar">
<sha256 value="89c5f029811b08c878f0b81dbb05e9626624c1fda4087a26871101e499a217ab" origin="Generated by Gradle"/>
</artifact>
<artifact name="snakeyaml-1.29.pom">
<sha256 value="c8d3dddbed64b4b1cc0f7e85c04588cf0fd44e84e0dae930de1a2d8b985e681c" origin="Generated by Gradle"/>
</artifact>
</component>
replace witness plugin with gradle dependency checksum verification (#223) * replace witness plugin with gradle builtin dependency checksum verification I noticed that a recent dependency change didn't needed checksum change. It was because the witness plugin only checked the listed checksums, not all the dependencies. If the dependency was not on the list, the new checksum was not verified. Gradle now has its own verification mechanism, see https://docs.gradle.org/current/userguide/dependency_verification.html After a dependency is added or a version is changed, the checksums could be regenerated using the following command. ``` gradle --write-verification-metadata sha256 help ```` The help task is just used to discover as much as possible dependencies, and if subsequent builds fail with a verification error, you can re-execute generation with the appropriate tasks to "discover" more dependencies I verified that all the checksums from the removed file are present in the new one. jcenter repository (used only for gradle shadow plugin) is replaced with gradlePluginPortal. jcenter is shutting down anyway and the checksums for shadow plugin and its dependencies were not added automatically to the xml file for some reason. * add javadoc and source as trusted artifacts Co-authored-by: woodser <woodser@protonmail.com>
2022-02-06 16:36:58 +00:00
<component group="org.zeromq" name="jeromq" version="0.5.2">
<artifact name="jeromq-0.5.2.jar">
<sha256 value="8c19e7148bee907597129b2fd706839c45db849c72a25285ec1674f0ffdabf8e" origin="Generated by Gradle"/>
</artifact>
<artifact name="jeromq-0.5.2.pom">
<sha256 value="4367abba02c31f1dce129b455652966b1703b554a9bc9ddbf33e96ca00cfe15c" origin="Generated by Gradle"/>
</artifact>
</component>
</components>
</verification-metadata>
Reference in a new issue Copy permalink