mirrors/bisq
1
0
Fork 0
mirror of https://github.com/bisq-network/bisq.git synced 2024-11-19 09:52:23 +01:00
Code Issues Packages Projects Releases Wiki Activity
cf56ae316e
bisq/gradle/verification-metadata.xml

1439 lines
87 KiB
XML
Raw Normal View History

Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
<?xml version="1.0" encoding="UTF-8"?>
<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.1.xsd">
<configuration>
<verify-metadata>true</verify-metadata>
<verify-signatures>false</verify-signatures>
Disable verification for javadoc and source jars Prior to this commit, IDEA would fail to build the project because it downloads javadoc and source jars that do not have entries in the verification file. These artifacts are now trusted by default as documented at https://docs.gradle.org/current/userguide/dependency_verification.html#sec:skipping-javadocs
2021-11-13 14:43:03 +01:00
<trusted-artifacts>
<trust file=".*-javadoc[.]jar" regex="true"/>
<trust file=".*-sources[.]jar" regex="true"/>
</trusted-artifacts>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</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>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="logback-core-1.1.11.pom">
<sha256 value="7199197992fb549a4b620f368a6726298360eb9ebb37e4ed16eb4e5ad2be0f25" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</component>
<component group="com.fasterxml" name="oss-parent" version="41">
<artifact name="oss-parent-41.pom">
<sha256 value="af650fa4dd400bc5769320bcef08ed93813f349cabe8213d469acafbbd945d8a" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<component group="com.fasterxml.jackson" name="jackson-base" version="2.12.1">
<artifact name="jackson-base-2.12.1.pom">
<sha256 value="93a8c78755a31977508021dbb3883c0dd740a06bb1c67ff4942e096c132419f5" origin="Manually computed by Alva"/>
</artifact>
</component>
Update to Gradle 7.6
2022-12-07 00:26:41 +01:00
<component group="com.fasterxml.jackson" name="jackson-bom" version="2.12.1">
<artifact name="jackson-bom-2.12.1.pom">
<sha256 value="083b20a4231bb0516d6e1a08248c9fbce473583a122a07fd2e0eadeff6908a38" origin="Generated by Gradle"/>
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.fasterxml.jackson" name="jackson-parent" version="2.12">
<artifact name="jackson-parent-2.12.pom">
<sha256 value="62aa1c1679ade09f173dbf1b6c32d35c55e75800238fd5e48f13aa4337c0875b" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</component>
<component group="com.fasterxml.jackson.core" name="jackson-annotations" version="2.12.1">
<artifact name="jackson-annotations-2.12.1.jar">
<sha256 value="203cefdfa6c81e6aa84e11f292f29ca97344a3c3bc0293abea065cd837592873" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-annotations-2.12.1.module">
<sha256 value="93a1d3d9c8d1d694431057ccbe9730e032921b1b2b166b1570017da1eeb6483e" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.fasterxml.jackson.core" name="jackson-core" version="2.12.1">
<artifact name="jackson-core-2.12.1.jar">
<sha256 value="cc899cb6eae0c80b87d590eea86528797369cc4feb7b79463207d6bb18f0c257" origin="Generated by Gradle"/>
</artifact>
<artifact name="jackson-core-2.12.1.module">
<sha256 value="7e4c0c921ccee0b555f0f5b36fd86707b4e556de5b02f3e6bfc315bc3fcd6fc4" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.fasterxml.jackson.core" name="jackson-databind" version="2.12.1">
<artifact name="jackson-databind-2.12.1.jar">
<sha256 value="f2ca3c28ebded59c98447d51afe945323df961540af66a063c015597af936aa0" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="jackson-databind-2.12.1.module">
<sha256 value="b493b42a9c95eebb3059e030d598005ebe5bed153cbd01c0dfccc814a0c37890" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.bisq-network" name="bitcoinj" version="42bbae9">
<artifact name="bitcoinj-42bbae9.jar">
<sha256 value="eccd3b5250d40ac3147d0e087e856ebaa8665720351b802d30ac53cf17b559c5" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="bitcoinj-42bbae9.pom">
<sha256 value="733017ea93e8818889da862cb6b509d55beb9ebacb08c390c3a525a0efdfe1b7" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Target BitcoinJ version with "Reduce log level of two messages" patch
2023-01-15 16:13:39 +01:00
<component group="com.github.bisq-network" name="bitcoinj" version="e1cb2a17998b6071b1a10ef17f80cbf424f4255f">
<artifact name="bitcoinj-e1cb2a17998b6071b1a10ef17f80cbf424f4255f.jar">
<sha256 value="efa682c13536ef11b6fe1cca2a1367eb8f6781776e4e24225b074df4dcb570fb" origin="Generated by Gradle"/>
</artifact>
<artifact name="bitcoinj-e1cb2a17998b6071b1a10ef17f80cbf424f4255f.pom">
<sha256 value="734ad905e656cecd09e4f96847cdd302f6c47c196c3162db57352f64eec465ed" origin="Generated by Gradle"/>
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.bisq-network" name="jsocks" version="43b004b5bcc468fb1213767853e1d8a54fd4a359">
<artifact name="jsocks-43b004b5bcc468fb1213767853e1d8a54fd4a359.jar">
<sha256 value="8ff45a70a9a927427618bfe6dab80b06a054f3da8addbad2f4228d0ab9cc03f6" origin="Generated by Gradle"/>
Fix guava dependency issue Problem: a NoSuchMethodError: 'java.util.stream.Collector com.google.common.collect.ImmutableMultiset.toImmutableMultiset()' exception was being thrown when testing the previously-merged upgrade to Gradle 7.3, as described at keybase://chat/bisq#testing/2466. Solution: This problem is similar to the issue reported at jeremylong/DependencyCheck#3221. The source of the problem was multiple conflicting guava jars on the runtime classpath. This commit upgrades to guava 30.1.1-jre which ensures a single jar on the classpath.
2021-11-21 12:01:34 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="jsocks-43b004b5bcc468fb1213767853e1d8a54fd4a359.pom">
<sha256 value="6831518f5f2b48cf63f3e8e6c43d12fd6dc1457f18ca61a5c87b20e43b4022a7" origin="Generated by Gradle"/>
Fix guava dependency issue Problem: a NoSuchMethodError: 'java.util.stream.Collector com.google.common.collect.ImmutableMultiset.toImmutableMultiset()' exception was being thrown when testing the previously-merged upgrade to Gradle 7.3, as described at keybase://chat/bisq#testing/2466. Solution: This problem is similar to the issue reported at jeremylong/DependencyCheck#3221. The source of the problem was multiple conflicting guava jars on the runtime classpath. This commit upgrades to guava 30.1.1-jre which ensures a single jar on the classpath.
2021-11-21 12:01:34 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="jsonrpc4j-1.6.0.bisq.1.module">
<sha256 value="186ae5ab78573247c2915edcd9317af1cbbd655a1baf58b7d9704992f695aed4" origin="Generated by Gradle"/>
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update missing hashes for tor 0.7.5 update
2022-10-17 11:14:32 +02:00
<component group="com.github.bisq-network.netlayer" name="parent" version="0.7.5">
<artifact name="parent-0.7.5.pom">
<sha256 value="43130d90d737cbaafa936fd6fc258cc5bb59c97fb07b435f98b86246d38d245b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.netlayer" name="tor" version="0.7.5">
<artifact name="tor-0.7.5.jar">
<sha256 value="84edece2d968e7a6f8c88e258d98600e8e75eb31b92ec3b0057aa39c298229b9" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-0.7.5.pom">
<sha256 value="a0dfe9ec9756b5c865eb082eab98c927a23084e5a079640bb7fa1b94fe2c1bb6" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.netlayer" name="tor.external" version="0.7.5">
<artifact name="tor.external-0.7.5.jar">
<sha256 value="b79ee3c3316e077a20db9b08e2b495344b6d3898a4da71614ae5b993105aee6b" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.external-0.7.5.pom">
<sha256 value="68a282002bf2b2acddfcecdb71960b31a1727f52b16a90e180212f9fa232f76f" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.netlayer" name="tor.native" version="0.7.5">
<artifact name="tor.native-0.7.5.jar">
<sha256 value="83f16fd3a87818a1265906168a18e3de823b2716908483fb903be67fa9965cff" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor.native-0.7.5.pom">
<sha256 value="85cf27c7ec6090918e325e8a17cd3f99b5a0af2e56ef15c32e029e807b45e3ee" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.tor-binary" name="tor-binary" version="580d31bdcf1fabccd38456aa084044064d89d5c1">
<artifact name="tor-binary-580d31bdcf1fabccd38456aa084044064d89d5c1.pom">
<sha256 value="9169ee132238730aee19f50e6c5c5764c64a88fd2b49c71988756bd98abcb6c3" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.tor-binary" name="tor-binary-geoip" version="580d31bdcf1fabccd38456aa084044064d89d5c1">
<artifact name="tor-binary-geoip-580d31bdcf1fabccd38456aa084044064d89d5c1.jar">
<sha256 value="5a1795e95128e8c6fb3381d1c31ac39f2ec4e4fc3a0262f3f9ac3c7987e0c87e" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-geoip-580d31bdcf1fabccd38456aa084044064d89d5c1.pom">
<sha256 value="82590ea62802a6ae5b59d905554e019f50fcf82cd3da475bdb052e7ddd233a9f" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux32" version="580d31bdcf1fabccd38456aa084044064d89d5c1">
<artifact name="tor-binary-linux32-580d31bdcf1fabccd38456aa084044064d89d5c1.jar">
<sha256 value="2516ce5549ef5687ef7f855db5940574fc9232ff3ba531fbc216275b8d51ae85" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux32-580d31bdcf1fabccd38456aa084044064d89d5c1.pom">
<sha256 value="e296c0099fc720e9765df8e47ac1ff6a890350089355305a5d6ef7ca0b235559" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.tor-binary" name="tor-binary-linux64" version="580d31bdcf1fabccd38456aa084044064d89d5c1">
<artifact name="tor-binary-linux64-580d31bdcf1fabccd38456aa084044064d89d5c1.jar">
<sha256 value="afc7ad5e1bc57e73aae55d9b022ff63f41f7c73a9a7603d4c24975288432daa1" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-linux64-580d31bdcf1fabccd38456aa084044064d89d5c1.pom">
<sha256 value="cd92edc30ea028fed031953d9e1e3cf88f8749850cf189837c1a19f70be5289f" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.tor-binary" name="tor-binary-macos" version="580d31bdcf1fabccd38456aa084044064d89d5c1">
<artifact name="tor-binary-macos-580d31bdcf1fabccd38456aa084044064d89d5c1.jar">
<sha256 value="5bfb2eaf7efe5d280d6b68e222c910cc6ae2a925e3d06fa35c6b5295ebf94651" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-macos-580d31bdcf1fabccd38456aa084044064d89d5c1.pom">
<sha256 value="c23a48685c597d10f584768c76ec02f098b751913c0eca73aaaee2477580ffc6" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.github.bisq-network.tor-binary" name="tor-binary-windows" version="580d31bdcf1fabccd38456aa084044064d89d5c1">
<artifact name="tor-binary-windows-580d31bdcf1fabccd38456aa084044064d89d5c1.jar">
<sha256 value="b5fbe9f9e2681b0cfdd0d8a26c7b216c38acfea74fe2103633fe7e81b6cc4bf7" origin="Generated by Gradle"/>
</artifact>
<artifact name="tor-binary-windows-580d31bdcf1fabccd38456aa084044064d89d5c1.pom">
<sha256 value="0428ee4b868d438d7e96e457bc71c249b68691a7332967d720741c6f04abeac6" origin="Generated by Gradle"/>
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.javaparser" name="javaparser-core" version="3.13.5">
<artifact name="javaparser-core-3.13.5.jar">
<sha256 value="3ad8087c59e6a13b699a4917897086ae30f9834b5d5718d88d1b321c887b461a" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="javaparser-core-3.13.5.pom">
<sha256 value="4371244f44169f05d831eef4a3975e8f02762260ee374aa5b195dd30bd79a98b" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.javaparser" name="javaparser-parent" version="3.13.5">
<artifact name="javaparser-parent-3.13.5.pom">
<sha256 value="083e6824737bd2b675882624151f0dcf2fb7540729d5e49f90c41d0540677073" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.javaparser" name="javaparser-symbol-solver-core" version="3.13.5">
<artifact name="javaparser-symbol-solver-core-3.13.5.jar">
<sha256 value="09adb3cda5efece7e62996bf8be43eeb831b1e649dd13ef161e327d3ba66cea3" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="javaparser-symbol-solver-core-3.13.5.pom">
<sha256 value="18a873ada89d1fbe5fb3beefcdea3be8848b3b535f2ff042c403eeab8b088fd1" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.javaparser" name="javaparser-symbol-solver-logic" version="3.13.5">
<artifact name="javaparser-symbol-solver-logic-3.13.5.jar">
<sha256 value="593a9659b70c0ef0677431d7ad8680ef9c86aa71deab9fb35db2b028d5de7973" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="javaparser-symbol-solver-logic-3.13.5.pom">
<sha256 value="1bf9d50f28c6f24c5aeda6c642e45a48cde22d94b5e52cd4cfa3d370ee3f69d6" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.javaparser" name="javaparser-symbol-solver-model" version="3.13.5">
<artifact name="javaparser-symbol-solver-model-3.13.5.jar">
<sha256 value="0d71c0d24d9f86181b198446ee8ddf18a597130877903c2276d3015ffe45383f" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="javaparser-symbol-solver-model-3.13.5.pom">
<sha256 value="39cf4dd454b1ed489afc7c89d0500163f282e214c34dc99ce3faf75bd2490c8e" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.github.jengelman.gradle.plugins" name="shadow" version="5.2.0">
<artifact name="shadow-5.2.0.jar">
<sha256 value="b748da66d6f11acef435e1f2e95151dab902bb2de23fc8af575b86237d6ba6c8" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="shadow-5.2.0.pom">
<sha256 value="54468f4cf5d16864b46dca4e96cd9359a6b720a3cfbff6d403f2486e31cf88f9" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="com.google" name="google" version="1">
<artifact name="google-1.pom">
<sha256 value="cd6db17a11a31ede794ccbd1df0e4d9750f640234731f21cff885a9997277e81" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</component>
<component group="com.google" name="google" version="5">
<artifact name="google-5.pom">
<sha256 value="e09d345e73ca3fbca7f3e05f30deb74e9d39dd6b79a93fee8c511f23417b6828" origin="Generated by Gradle"/>
Add verification metadata for MacOS x86 artifacts This commit updates the verification-metadata.xml file to include osx-x86_64 variants of protoc dependencies.
2021-11-13 13:33:26 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</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"/>
Add Windows artifact hashes
2021-11-15 13:26:05 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="annotations-4.1.1.4.pom">
<sha256 value="e4bb54753c36a27a0e5d70154a5034fedd8feac4282295034bfd483d6c7aae78" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<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"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="jsr305-3.0.2.pom">
<sha256 value="19889dbdf1b254b2601a5ee645b8147a974644882297684c798afe5d63d78dfe" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<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"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="gson-2.8.5.pom">
<sha256 value="b8308557a7fccc92d9fe7c8cd0599258b361285d2ecde7689eda98843255a092" origin="Generated by Gradle"/>
Add missing dependency verification entries This fixes the CI build failure at https://github.com/bisq-network/bisq/runs/4198811212?check_suite_focus=true#step:6:306 by adding missing entries for findbugs, jsr305 and various netty artifacts. It is not clear why these artifacts were required under linux and not under MacOS.
2021-11-13 14:56:49 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="gson-2.8.6.pom">
<sha256 value="2174415a647332d30fda04bd1cfc708a3ecc84eaf7517f596188d8244e103911" origin="Generated by Gradle"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</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>
<component group="com.google.code.gson" name="gson-parent" version="2.8.6">
<artifact name="gson-parent-2.8.6.pom">
<sha256 value="3736463859ec19267295e894940ae82a8f684413031122fe35ce7cff7e30a774" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="error_prone_annotations-2.2.0.pom">
<sha256 value="5e0258ea1ba4e51a133742680bc22448f7ab214be4073e8619f645ef1be42dd5" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="error_prone_annotations-2.5.1.pom">
<sha256 value="983ad7fe0fa6f6f91e2d20477f5089eccc3f4d8ec6c51d6eb45583970e279d3c" 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>
<component group="com.google.errorprone" name="error_prone_parent" version="2.2.0">
<artifact name="error_prone_parent-2.2.0.pom">
<sha256 value="c460902ddf5ece68832c6b271ce52a0928b05cf3a6ac81a8f548c73cbd541138" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.errorprone" name="error_prone_parent" version="2.5.1">
<artifact name="error_prone_parent-2.5.1.pom">
<sha256 value="a17a7677482a3a51a45f5e08140072acd332ccb12f23899b0052d80a729c2e52" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<component group="com.google.gradle" name="osdetector-gradle-plugin" version="1.6.0">
<artifact name="osdetector-gradle-plugin-1.6.0.pom">
<sha256 value="f6cd28bb7aa1b704faedf9b9a65d035476b9c6c3ca8cda5d7b76e0e3a22dcfd6" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.gradle" name="osdetector-gradle-plugin" version="1.7.0">
<artifact name="osdetector-gradle-plugin-1.7.0.jar">
<sha256 value="dbda2178c14ed6b93a184b1acbf38d72107002252668c111cf411eca37e41ca6" origin="Generated by Gradle"/>
</artifact>
<artifact name="osdetector-gradle-plugin-1.7.0.pom">
<sha256 value="e81632c2ee9aa48e7ecf0547512c1c386560c0d46a958ee50550f7ebddf13517" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="failureaccess-1.0.1.pom">
<sha256 value="e96042ce78fecba0da2be964522947c87b40a291b5fd3cd672a434924103c4b9" 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>
<artifact name="guava-27.0.1-jre.pom">
<sha256 value="6a8dd041f23a6bb14a86e440fccb993537b62271357a0dac0a3cb0ff39158f36" 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>
<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="27.0.1-jre">
<artifact name="guava-parent-27.0.1-jre.pom">
<sha256 value="317e88291262e0cf2805e956c18850f1d4565c85c2e1112f5d9d08ab1732e696" 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>
<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>
<artifact name="listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.pom">
<sha256 value="18d4b1db26153d4e55079ce1f76bb1fe05cdb862ef9954a88cbcc4ff38b8679b" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.inject" name="guice" version="5.0.1">
<artifact name="guice-5.0.1.jar">
<sha256 value="3bae18be3e0f0940375d1ebdd2f3b84d87ae16026ae663b2f5d4667fe5b04036" origin="Generated by Gradle"/>
</artifact>
<artifact name="guice-5.0.1.pom">
<sha256 value="0d2938606bd299aa90c99aea1dbeee86732e42b198a37a47acc92ca1360595db" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.inject" name="guice-parent" version="5.0.1">
<artifact name="guice-parent-5.0.1.pom">
<sha256 value="903bbb2fb8584c3ab3b532556c2fa8d0860c5e74c667f6681720b445b2226337" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="j2objc-annotations-1.1.pom">
<sha256 value="f0c98c571e93a7cb4dd18df0fa308f0963e7a0620ac2d4244e61e709d03ad6be" origin="Generated by Gradle"/>
</artifact>
</component>
<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.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>
<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>
<artifact name="protobuf-gradle-plugin-0.8.17.pom">
<sha256 value="3afaad5f2a249d1b3021d7733d97cb4e1bdd7a959106c6da4bee3ce0bce0b632" origin="Generated by Gradle"/>
</artifact>
</component>
<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-parent" version="3.19.1">
<artifact name="protobuf-parent-3.19.1.pom">
<sha256 value="83d413b2a79d6357d2ca78fd623143424e8f6ecc72cfa83bf2ae2ae258a93a44" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.protobuf" name="protoc" version="3.19.1">
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="protoc-3.19.1-linux-x86_64.exe">
<sha256 value="0b1099f537d44ee862b0c3708f32f1d66cfd76e2e2c1437f0c57a98476c20605" origin="Generated by Gradle"/>
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="protoc-3.19.1-osx-x86_64.exe">
<sha256 value="3431ad66f3bb24cd5196e92a561b0e03bf2906c894bc94d131daaa637094abac" origin="Generated by Gradle"/>
</artifact>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="protoc-3.19.1-windows-x86_64.exe">
<sha256 value="06f65a95ee0fb212c45473e0e65cca824e4634b291fe8dd666068edf51e6ca4c" origin="Manually computed by Alva"/>
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="protoc-3.19.1.pom">
<sha256 value="71a3da76c0c3b7bedb71c1e65f18f47193cc73ef1f27fc26b0a70715794019b7" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="com.google.zxing" name="core" version="2.0">
<artifact name="core-2.0.jar">
<sha256 value="11aae8fd974ab25faa8208be50468eb12349cd239e93e7c797377fa13e381729" origin="Generated by Gradle"/>
</artifact>
<artifact name="core-2.0.pom">
<sha256 value="2bf92ca16394dbf2906b03c5d2c749f6c280b9289bdc469bb263590a117d9957" 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>
<artifact name="javase-2.0.pom">
<sha256 value="5715c1c41276eeb86793d061d8251f545442f567a920125eca7e71c54ca39bfa" 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>
<artifact name="jcsv-1.4.0.pom">
<sha256 value="5788f3fa57cd4cb75db096d5286b948c8a8cb8897875759eda653a29758289d6" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="jfoenix-9.0.10.pom">
<sha256 value="b24601bd9cc1bad8a9a6ca1586715b488cf2d13ea0fce1acb65dd7c73510176a" 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>
<artifact name="make-it-easy-4.0.1.pom">
<sha256 value="1526287fb2372207be56c8e98b6a1621db9a88774331ba0c603b2710ed365f7d" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<component group="commons-io" name="commons-io" version="2.5">
<artifact name="commons-io-2.5.pom">
<sha256 value="28ebb2998bc7d7acb25078526971640892000f3413586ff42d611f1043bfec30" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="commons-io-2.6.pom">
<sha256 value="0c23863893a2291f5a7afdbd8d15923b3948afd87e563fa341cdcf6eae338a60" 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>
<artifact name="commons-lang-2.6.pom">
<sha256 value="ed76b8891c30b566289c743656f8a4d435986982438d40c567c626233247e711" 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>
<artifact name="fontawesomefx-8.0.0.pom">
<sha256 value="4e4b2f9dc963f8b6437d8e8a9b96fdb82c4e869060b59e5d18acde11aa1dc977" 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>
<artifact name="fontawesomefx-commons-9.1.2.pom">
<sha256 value="ab4be6f30afd349b02bda8b6097ed5e229d2b5d3e9568c9cc69e36130c49150c" 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>
<artifact name="fontawesomefx-materialdesignfont-2.0.26-9.1.2.pom">
<sha256 value="1bb0abb32c6556c63fdb5ce181a4d38a81e385823915dbd9ebb65116ab99a021" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="io.github.microutils" name="kotlin-logging" version="1.5.4">
<artifact name="kotlin-logging-1.5.4.jar">
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<sha256 value="4992504fd3c6ecdf9ed10874b9508e758bb908af9e9d7af19a61e9afb6b7e27a" origin="Generated by Gradle"/>
</artifact>
<artifact name="kotlin-logging-1.5.4.pom">
<sha256 value="4728eddd64e6ae3e1f205a775c6a327b24bd990b86d528584a17450a8b5f00d6" origin="Generated by Gradle"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
</component>
<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>
<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>
<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>
<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>
<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>
<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>
<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>
<component group="io.grpc" name="protoc-gen-grpc-java" version="1.42.1">
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="protoc-gen-grpc-java-1.42.1-linux-x86_64.exe">
<sha256 value="5596b69eb69ed508bc69307f14340be702bdee2ff0ed33c1cafde02aefc9faaf" origin="Generated by Gradle"/>
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="protoc-gen-grpc-java-1.42.1-osx-x86_64.exe">
<sha256 value="f343841e08c9cbffdda92278f01f4ab9c2afb91b6125047e4c8d0aaf59736764" origin="Generated by Gradle"/>
</artifact>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="protoc-gen-grpc-java-1.42.1-windows-x86_64.exe">
<sha256 value="cf8a24fd65e2e243aed74f79589d9b0194fd1f7a70063fd523cc0baeb44532a9" origin="Manually computed by Alva"/>
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="protoc-gen-grpc-java-1.42.1.pom">
<sha256 value="9856d0a3e07df312825e698082b6ec6401cd15814ca74092ae58084f4925e784" origin="Generated by Gradle"/>
</artifact>
</component>
<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.module">
<sha256 value="84a12f34817d1f2f79df810bcbaacb29900678384d3dd0502df0bd963a4f3fdb" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="javax.annotation-api-1.2.pom">
<sha256 value="52d73f35f7e638ce3cb56546f879c20e7f7019f72aa20cde1fa80e97865dfd40" origin="Generated by Gradle"/>
</artifact>
</component>
<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="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>
<artifact name="junit-4.13.1.pom">
<sha256 value="c68defdedaaaeae1432e12a5302bf2bfa05057d8b5acc65aaa3f3d9853ff40d6" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="kr.motd.maven" name="os-maven-plugin" version="1.7.0">
<artifact name="os-maven-plugin-1.7.0.jar">
<sha256 value="943053501a429e53d1c4d62152eec125fa36620e0dc66b7390a895097cfdeace" origin="Generated by Gradle"/>
</artifact>
<artifact name="os-maven-plugin-1.7.0.pom">
<sha256 value="c4f56a8eeaa5269efa05db01e3130905ff5bdb87eb2ae3e766154e9aea183ba6" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="byte-buddy-1.11.19.pom">
<sha256 value="8102b6dcfa0ab794b734b702526e8881c5feb488190556f6962fab9cd9144088" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="byte-buddy-agent-1.11.19.pom">
<sha256 value="04882c341ca85d5fcd338837ccd5e62b73c5e262af0845537d656bb37b2956cf" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.bytebuddy" name="byte-buddy-parent" version="1.11.19">
<artifact name="byte-buddy-parent-1.11.19.pom">
<sha256 value="1bdb848e7ec01925df8f51c19f8320edd46e72d3dffd30e03af80ea01e1cfc02" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="net.glxn" name="qrgen" version="1.3">
<artifact name="qrgen-1.3.jar">
<sha256 value="c85d9d8512d91e8ad11fe56259a7825bd50ce0245447e236cf168d1b17591882" origin="Generated by Gradle"/>
</artifact>
<artifact name="qrgen-1.3.pom">
<sha256 value="ff99b0ecd90de84e2e0a4d8bd3edea59c926005e3354f24ce294390a69112879" 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.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>
<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="16">
<artifact name="apache-16.pom">
<sha256 value="9f85ff2fd7d6cb3097aa47fb419ee7f0ebe869109f98aba9f4eca3f49e74a40e" 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="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="7">
<artifact name="apache-7.pom">
<sha256 value="1397ce1db433adc9f223dbf07496d133681448751f4ae29e58f68e78fb4b6c25" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.ant" name="ant" version="1.9.7">
<artifact name="ant-1.9.7.jar">
<sha256 value="9a5dbe3f5f2cb91854c8682cab80178afa412ab35a5ab718bf39ce01b3435d93" origin="Generated by Gradle"/>
</artifact>
<artifact name="ant-1.9.7.pom">
<sha256 value="1b9fbd4f325a71e99b279080d63084f12d884d42081af298f9e553e1fe0cd74a" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.ant" name="ant-launcher" version="1.9.7">
<artifact name="ant-launcher-1.9.7.jar">
<sha256 value="bc376f6d6cb586229f451ac459faf1443b144c26d6647618ec9cba60e54c2b79" origin="Generated by Gradle"/>
</artifact>
<artifact name="ant-launcher-1.9.7.pom">
<sha256 value="d7bcdd3ab0ff55edbe1b96d06f06dac2135ec63b5a7c32cef3a436b49c9eee27" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.apache.ant" name="ant-parent" version="1.9.7">
<artifact name="ant-parent-1.9.7.pom">
<sha256 value="75d2cef64c65ccbdd2faf7261e53b444778d56d338763154e30fada4a41d1215" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<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>
<component group="org.apache.commons" name="commons-parent" version="17">
<artifact name="commons-parent-17.pom">
<sha256 value="96e718baf534874ee62ce4d42de265f2ddacd88391a540e030d59d98fa7c4408" origin="Generated by Gradle"/>
</artifact>
</component>
<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="39">
<artifact name="commons-parent-39.pom">
<sha256 value="87cd27e1a02a5c3eb6d85059ce98696bb1b44c2b8b650f0567c86df60fa61da7" 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="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>
<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>
<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>
<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-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-parent" version="11">
<artifact name="httpcomponents-parent-11.pom">
<sha256 value="a901f87b115c55070c7ee43efff63e20e7b02d30af2443ae292bf1f4e532d3aa" 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.logging" name="logging-parent" version="3">
<artifact name="logging-parent-3.pom">
<sha256 value="763a2ec2b8094d4161deb6c264b1262085b9be30bf3a31c2ce137242e57722a7" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
Update to Gradle 7.6
2022-12-07 00:26:41 +01:00
<component group="org.apache.logging.log4j" name="log4j" version="2.17.1">
<artifact name="log4j-2.17.1.pom">
<sha256 value="967abc024443a9cb096935559af5e9ad6f0ff61375f84b27d440d2fa70806b09" origin="Generated by Gradle"/>
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02: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>
Update to Gradle 7.6
2022-12-07 00:26:41 +01:00
<component group="org.apache.logging.log4j" name="log4j-api" version="2.17.1">
<artifact name="log4j-api-2.17.1.jar">
<sha256 value="b0d8a4c8ab4fb8b1888d0095822703b0e6d4793c419550203da9e69196161de4" origin="Generated by Gradle"/>
</artifact>
<artifact name="log4j-api-2.17.1.pom">
<sha256 value="1e2acef3220b29be10ae099728b158b18d943f91a193cc4501bb42f929c1e88a" origin="Generated by Gradle"/>
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="org.apache.logging.log4j" name="log4j-core" version="2.17.0">
<artifact name="log4j-core-2.17.0.jar">
<sha256 value="65c33dc9b24a5e5f6cacae62680641582894749c7bf16c951032ef92f3e12a60" origin="Generated by Gradle"/>
</artifact>
<artifact name="log4j-core-2.17.0.pom">
<sha256 value="5944274eb95590ace7c26201d9725b4ab1c7654d2953ae7cc26d73ffde4068be" origin="Generated by Gradle"/>
</artifact>
</component>
Update to Gradle 7.6
2022-12-07 00:26:41 +01:00
<component group="org.apache.logging.log4j" name="log4j-core" version="2.17.1">
<artifact name="log4j-core-2.17.1.jar">
<sha256 value="c967f223487980b9364e94a7c7f9a8a01fd3ee7c19bdbf0b0f9f8cb8511f3d41" origin="Generated by Gradle"/>
</artifact>
<artifact name="log4j-core-2.17.1.pom">
<sha256 value="0bbb3bf6d4d22a1bfa3c3c0927c29410af14a0fb26e3b02b93726f5c7e98aafd" origin="Generated by Gradle"/>
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02: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>
<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>
<artifact name="diff-match-patch-1.2.pom">
<sha256 value="e077d81dff9d92244580e573fd4bfede593685e80ba9d13f027d6c5fc57ee8c5" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.bouncycastle" name="bcprov-jdk15to18" version="1.63">
<artifact name="bcprov-jdk15to18-1.63.jar">
<sha256 value="82c28318b178da751d174b1adf6c43e0199f0fcf80a7bf6483caa226ae0d30b3" origin="Generated by Gradle"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="bcprov-jdk15to18-1.63.pom">
<sha256 value="40bc5efb0aa8ecb08d180edb4758255648877df6fd44ef0815db960a6c4d828f" origin="Generated by Gradle"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="checker-qual-2.5.2.pom">
<sha256 value="dc4cd438a36462d013c2338c8e206d102a322a00f33729e8955ee219859c9ede" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="checker-qual-3.8.0.pom">
<sha256 value="7e6d59e2d3bc01b1f04fa3667193a6d4170199b14fba53a7a8e36bf7602239a7" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Gradle: Create bisq.java-conventions precompiled script
2023-02-05 21:58:46 +01:00
<component group="org.codehaus.groovy" name="groovy" version="3.0.13">
<artifact name="groovy-3.0.13.jar">
<sha256 value="044569c20b1438263470585627da1b2c9722f1fb8d89f94e78c0ff219abd0146" origin="Manually computed by Alva"/>
</artifact>
<artifact name="groovy-3.0.13.pom">
<sha256 value="9a1cb18a8a01fe42da530f4059cedfd0948d6e8cf3100dae1ee2977c1ea55acc" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-ant" version="3.0.13">
<artifact name="groovy-ant-3.0.13.pom">
<sha256 value="6f07c9dbf501d45c43e40d0b9b09d6e92c4681d9d61f1867636a401febbc9092" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-astbuilder" version="3.0.13">
<artifact name="groovy-astbuilder-3.0.13.pom">
<sha256 value="208aa8d42692a4d19eca96f87c5c62a2c97a284389a5803a33e530bbd6064f09" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-console" version="3.0.13">
<artifact name="groovy-console-3.0.13.pom">
<sha256 value="00e84cdda323531d4212f8c58ade3924ddb1d9b1f3360973a8a240b8032044c3" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-datetime" version="3.0.13">
<artifact name="groovy-datetime-3.0.13.pom">
<sha256 value="89c4216d180d7e928e633c8b415a857f17e28153c7384dbc392fca48044286d3" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-dateutil" version="3.0.13">
<artifact name="groovy-dateutil-3.0.13.pom">
<sha256 value="d7358a271f3eb1aad7c7df80a57362358261932a8db59b7df49d655dd495db7e" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-groovydoc" version="3.0.13">
<artifact name="groovy-groovydoc-3.0.13.pom">
<sha256 value="034846307b8283ac60d33678731992e5eff4508955fd570c6d6fc6e7d4006cee" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-json" version="3.0.13">
<artifact name="groovy-json-3.0.13.pom">
<sha256 value="0ee3f90ab537028eb9bcc1d9e6eb01515bbbb5c03cb16cc72fbda85f5da63952" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-nio" version="3.0.13">
<artifact name="groovy-nio-3.0.13.pom">
<sha256 value="fcef4d828c5d5dd9094492ab21c9b80dfec69062615cdcfca889d730322b62c5" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-sql" version="3.0.13">
<artifact name="groovy-sql-3.0.13.pom">
<sha256 value="3e1f2a2a8c79d2af4c8eb67bff4479894492fab7a5bfd39132c72f4c80657a4b" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-templates" version="3.0.13">
<artifact name="groovy-templates-3.0.13.pom">
<sha256 value="ee7ca0364ca13cddade1a624ab7989dffeedc9d19b4e13e99ec172c78fdec174" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-test" version="3.0.13">
<artifact name="groovy-test-3.0.13.pom">
<sha256 value="55c0eafdb4d09619e2456a940f29d88ff585a4034bfd565912d6109285e04b9d" origin="Manually computed by Alva"/>
</artifact>
</component>
<component group="org.codehaus.groovy" name="groovy-xml" version="3.0.13">
<artifact name="groovy-xml-3.0.13.pom">
<sha256 value="945e632416fa6931d6533042b6b9584f59d827cec1533eab147ddee334a7687e" origin="Manually computed by Alva"/>
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="animal-sniffer-annotations-1.17.pom">
<sha256 value="e956ab5d2eb48fabae12300d0cd2d3294d4a2a41abc2068c23cb4d60ad76cbe5" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.codehaus.mojo" name="animal-sniffer-parent" version="1.17">
<artifact name="animal-sniffer-parent-1.17.pom">
<sha256 value="18a03df16e2a184c582db7b125633c15fb7714027a84c1b532d72933dc08b81f" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.codehaus.mojo" name="mojo-parent" version="40">
<artifact name="mojo-parent-40.pom">
<sha256 value="fc648dcdc404f8bf66e0583914ecf980176618201227bea114fae85043cb755e" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
</component>
<component group="org.codehaus.plexus" name="plexus" version="4.0">
<artifact name="plexus-4.0.pom">
<sha256 value="0a1b692d7fcc90d6a45dae2e50f4660d48f7a44504f174aa60ef34fbe1327f6a" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.codehaus.plexus" name="plexus-utils" version="3.0.24">
<artifact name="plexus-utils-3.0.24.jar">
<sha256 value="83ee748b12d06afb0ad4050a591132b3e8025fbb1990f1ed002e8b73293e69b4" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="plexus-utils-3.0.24.pom">
<sha256 value="11067f6a75fded12bcdc8daf7a66ddd942ce289c3daf88a3fe0f8b12858a2ee6" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="easybind-1.0.3.pom">
<sha256 value="28323c619c05bd0ef05bae81cd056b04f382d7d09ae9e46311e4ec828b611f2a" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="hamcrest-all-1.3.pom">
<sha256 value="5bff685d8d3093bb6d02e0575af804562d3be709409bcc719d9e34bad65339b0" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.hamcrest" name="hamcrest-core" version="1.3">
<artifact name="hamcrest-core-1.3.jar">
<sha256 value="66fdef91e9739348df7a096aa384a5685f4e875584cce89386a7a47251c4d8e9" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="hamcrest-core-1.3.pom">
<sha256 value="fde386a7905173a1b103de6ab820727584b50d0e32282e2797787c20a64ffa93" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.javamodularity" name="moduleplugin" version="1.8.2">
<artifact name="moduleplugin-1.8.2.jar">
<sha256 value="f079128b30745db5392c555cf186a97b7face40471ddfce1a0930d1a0400d696" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="moduleplugin-1.8.2.pom">
<sha256 value="715f7c37fd97e9e7c396a3f35f2065d88e6ddc504adf5448f52332077fc4e95f" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.javassist" name="javassist" version="3.24.0-GA">
<artifact name="javassist-3.24.0-GA.jar">
<sha256 value="aba81efa678b621203fb89aeff81d6f126f7a9dd709401e5609c42976684ae23" origin="Generated by Gradle"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="javassist-3.24.0-GA.pom">
<sha256 value="c9d3790f030276541d118a11be67fd271bf81e301b962780e542c2e5f636c1b1" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.jdom" name="jdom2" version="2.0.6">
<artifact name="jdom2-2.0.6.jar">
<sha256 value="1345f11ba606d15603d6740551a8c21947c0215640770ec67271fe78bea97cf5" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="jdom2-2.0.6.pom">
<sha256 value="47b23a79fe336b741b82434c6e049d68165256e405e75c10921fd72fa8a65d8d" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.jetbrains" name="annotations" version="13.0">
<artifact name="annotations-13.0.jar">
<sha256 value="ace2a10dc8e2d5fd34925ecac03e4988b2c0f851650c94b8cef49ba1bd111478" origin="Generated by Gradle"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="annotations-13.0.pom">
<sha256 value="965aeb2bedff369819bdde1bf7a0b3b89b8247dd69c88b86375d76163bb8c397" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="kotlin-stdlib-1.3.41.pom">
<sha256 value="785b5b66f1146317d5ed5b18c8e0c10f83cd5c909434c799a4da9823f028cd63" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="kotlin-stdlib-common-1.3.41.pom">
<sha256 value="d2e537cd1f7705276242d8cc903a0286b6dc86b41b6e728e967ef719022f2e15" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="kotlin-stdlib-jdk7-1.3.41.pom">
<sha256 value="54c3962d2cf839d41bbee8b4817a6b2d06990c305c2efea655f64973d468a5fd" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="kotlin-stdlib-jdk8-1.3.41.pom">
<sha256 value="e3856758c3bb08b7c97ddcd493521c5e0bd0741717c93b292bf1a541513af082" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.jooq" name="joor" version="0.9.13">
<artifact name="joor-0.9.13.jar">
<sha256 value="4c64dcec5c3350d74527b8fb64647df63673cb272a7e34a9f3575d6e01315c3b" origin="Generated by Gradle"/>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="joor-0.9.13.pom">
<sha256 value="9105d34daa35bbebc34c3a238e2cd0f975849823665ba65799f826033005bf4b" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<component group="org.junit" name="junit-bom" version="5.7.0">
<artifact name="junit-bom-5.7.0.module">
<sha256 value="25de454b3add67654d6691b53de7593b502967b5ff549547b104d7961f1a52bd" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="junit-bom-5.7.0.pom">
<sha256 value="35fb15f8d0bee2b5900a22832762366552f9a349c56ced60ba123ce47738ff00" origin="Manually computed by Alva"/>
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="junit-jupiter-api-5.7.0.module">
<sha256 value="d1a7bae6cd44ad6d96715261410eef2338a494436d667280d1373a47c17e241c" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="junit-jupiter-engine-5.7.0.module">
<sha256 value="c36bda48228eef5c40cdc9a9d6303bb848382cdb0884b3677d49182b4ec7a1a4" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="junit-jupiter-params-5.7.0.module">
<sha256 value="23561cb313916ed459a3a4c325c1573f7dc41f89c14fbea4328aa8c87782baaf" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="junit-platform-commons-1.7.0.module">
<sha256 value="b0a5c7a1b7e409d1f5cc963d9aea1c77c34b90e163d6842a4489c6aa07ff8ee2" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01: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"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
Update verification-metadata.xml Remove classpath to springframework Signed-off-by: HenrikJannsen <boilingfrog@gmx.com>
2022-11-25 18:37:02 +01:00
<artifact name="junit-platform-engine-1.7.0.module">
<sha256 value="6510a9fa881cef42d41485538dbc54749426db1e0b14ec433915ea5f2448079a" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02: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"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="mockito-core-4.0.0.pom">
<sha256 value="9146f147483ae9dfdb226eb928e81926122fadc1665648262e6e095d15762ebf" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="org.objenesis" name="objenesis" version="3.2">
<artifact name="objenesis-3.2.jar">
<sha256 value="03d960bd5aef03c653eb000413ada15eb77cdd2b8e4448886edf5692805e35f3" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="objenesis-3.2.pom">
<sha256 value="4e10adf1477b8c711b45b8a15eb960f6b44871f5e1def38f16681348aa166b0c" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</component>
<component group="org.objenesis" name="objenesis-parent" version="3.2">
<artifact name="objenesis-parent-3.2.pom">
<sha256 value="0859ba0d5cfeefb13964e5862c036faa48a0bccff4932638fb13fe3445df33f7" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="org.openjfx" name="javafx" version="16">
<artifact name="javafx-16.pom">
<sha256 value="18d9784212d04475bfe4a5f4038e0fc78146f9a721eb6b9a52955d3b4b20d3ca" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
</component>
<component group="org.openjfx" name="javafx-base" version="16">
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-base-16-linux.jar">
<sha256 value="b825e220d685ecbd77e76f2cd52793132e6c9a10e23ee3361673cb29033413c0" origin="Generated by Gradle"/>
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="javafx-base-16-mac.jar">
<sha256 value="8cb4a023706d392d0a733aaee41be839e8418448ab0090a8115a9b909d595c77" origin="Generated by Gradle"/>
</artifact>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-base-16-win.jar">
<sha256 value="23abcdffb6f92d8b37531080682034d01c177f1229118a2f7646331c51c6ed63" origin="Manually computed by Alva"/>
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="javafx-base-16.jar">
<sha256 value="036955291b3633b6e11106df315f7a561218d31dcb4280078fe4d2414925f557" origin="Generated by Gradle"/>
</artifact>
<artifact name="javafx-base-16.pom">
<sha256 value="09fe0f2eda8b6f3d4c55b28e32b6b7b2782847add96a686d3048753baa781901" origin="Generated by Gradle"/>
Use Spring dependency-management plugin in pricenode This is in preparation for addressing log4j 2 zero day exploit described at https://www.lunasec.io/docs/blog/log4j-zero-day/. See full details in the next commit. Bringing in the dependency-management plugin results in many changes to our Gradle verification metadata file, but all are BOM / POM / Module manifests. No additional jar or code dependencies have been whitelisted with this change.
2021-12-10 10:34:09 +01:00
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="org.openjfx" name="javafx-controls" version="16">
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-controls-16-linux.jar">
<sha256 value="fd0aba38a0dde9836845c6d671501f4c30e6cff6f2d72748f75742dbcfc74df9" origin="Generated by Gradle"/>
</artifact>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<artifact name="javafx-controls-16-mac.jar">
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
<sha256 value="4add6fdf120ab9c784dc6e700c158d411d9371aaba7bbb61ad9f9d016f2cce44" origin="Generated by Gradle"/>
</artifact>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-controls-16-win.jar">
<sha256 value="a7f6e4757163c38a5e6cf26b426e9daf788ad1b57513111d362b3bbbc298d13b" origin="Manually computed by Alva"/>
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
<artifact name="javafx-controls-16.jar">
<sha256 value="dfdbe63f9717b2cd84c9fd34b28a8ddffdbe25cc1e4c2ff9f171f07ca725e0f4" origin="Generated by Gradle"/>
</artifact>
<artifact name="javafx-controls-16.pom">
<sha256 value="1769aa2547256cfe316387d78375056587283b63f0614fa6e9b59231ef90edd0" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.openjfx" name="javafx-fxml" version="16">
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-fxml-16-linux.jar">
<sha256 value="65249a5a47357283f21c5fa85b2e91255f7e5b0b86a2ec3dd2cc220541d7ae0b" origin="Generated by Gradle"/>
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
<artifact name="javafx-fxml-16-mac.jar">
<sha256 value="b722e590930180ff7c43d34281202251e1fe8d1f81b16098cda78600780b7f46" origin="Generated by Gradle"/>
</artifact>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-fxml-16-win.jar">
<sha256 value="e8313ffb783c26acbbc1267448bbfdf2f05126e5845a06c6f29a43db7483606d" origin="Manually computed by Alva"/>
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
<artifact name="javafx-fxml-16.pom">
<sha256 value="7b3b1a717f5d3a67f1dadcc880de3677a25a5d4e8004b75c61cec8b044b013cd" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.openjfx" name="javafx-graphics" version="16">
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-graphics-16-linux.jar">
<sha256 value="a2f5e1ea5aeb3ae57e63a1c853a4edf1e38b6f2fe76997ab864ad8b3c54bed53" origin="Generated by Gradle"/>
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
<artifact name="javafx-graphics-16-mac.jar">
<sha256 value="23a67ad877f283039a20dd827f68988c1f952fe4958d039c006762883f1f04ab" origin="Generated by Gradle"/>
</artifact>
Fix broken Gradle Dependency Verification The following artifacts failed verification: - javafx-base-16-linux.jar (org.openjfx:javafx-base:16) from repository MavenRepo - javafx-controls-16-linux.jar (org.openjfx:javafx-controls:16) from repository MavenRepo - javafx-fxml-16-linux.jar (org.openjfx:javafx-fxml:16) from repository MavenRepo - javafx-graphics-16-linux.jar (org.openjfx:javafx-graphics:16) from repository MavenRepo - protoc-3.19.1-linux-x86_64.exe (com.google.protobuf:protoc:3.19.1) from repository MavenRepo - protoc-gen-grpc-java-1.42.1-linux-x86_64.exe (io.grpc:protoc-gen-grpc-java:1.42.1) from repository MavenRepo - jackson-base-2.12.1.pom - protoc-3.19.1-windows-x86_64.exe - protoc-gen-grpc-java-1.42.1-windows-x86_64.exe - junit-bom-5.7.0.pom - javafx-base-16-win.jar - javafx-controls-16-win.jar - javafx-fxml-16-win.jar - javafx-graphics-16-win.jar
2022-12-06 19:34:17 +01:00
<artifact name="javafx-graphics-16-win.jar">
<sha256 value="78124668c64db443cf3e105b9c2f6d7061e7c72ad5ad2de63a13adc46ef2ca8c" origin="Manually computed by Alva"/>
</artifact>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
<artifact name="javafx-graphics-16.jar">
<sha256 value="77533b2922a853a3e1350c8e6650f6cf746000d20efef69119c6324086883b95" origin="Generated by Gradle"/>
</artifact>
<artifact name="javafx-graphics-16.pom">
<sha256 value="b8fb99688eccae62be724bd72b34dfff1f8e1cddbe44649f5ef9a082e520c47e" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.openjfx" name="javafx-plugin" version="0.0.10">
<artifact name="javafx-plugin-0.0.10.jar">
<sha256 value="d03e96d9e27a7461bce6c05b537d36c22dc84ecb94d5c05d5ee967577a203ed5" origin="Generated by Gradle"/>
</artifact>
<artifact name="javafx-plugin-0.0.10.pom">
<sha256 value="b3d28522fe9423202d79d1cf87c4afa18ebdd44ea2e9a9dbcf5faf289d65318b" origin="Generated by Gradle"/>
</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>
<component group="org.ow2.asm" name="asm" version="7.0-beta">
<artifact name="asm-7.0-beta.jar">
<sha256 value="ba84438f0f08ae2c2f85423dc3628361d20197c46a194687defdf63ed1896a3a" origin="Generated by Gradle"/>
</artifact>
<artifact name="asm-7.0-beta.pom">
<sha256 value="2d85484e0c0dd935e38edec52a33267ea1d50eb06d4c2ffb90d444c089571f86" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.ow2.asm" name="asm-analysis" version="7.0-beta">
<artifact name="asm-analysis-7.0-beta.jar">
<sha256 value="4d2b20a1fb44acb33b0ddb80be58b2ad7838c1fb520282a655a1217b3c6acf19" origin="Generated by Gradle"/>
</artifact>
<artifact name="asm-analysis-7.0-beta.pom">
<sha256 value="7a068ba0c921fe69824731f6a1b14f86ff0828a0c5941e5c24b6b501e2f6e69f" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.ow2.asm" name="asm-commons" version="7.0-beta">
<artifact name="asm-commons-7.0-beta.jar">
<sha256 value="3d8ec2534b883541b966e6dde9004967d34f7311789028afc92e2e066867dac4" origin="Generated by Gradle"/>
</artifact>
<artifact name="asm-commons-7.0-beta.pom">
<sha256 value="2b30b9d132f43dfba6ebced3c9661b1b5c60187dfc4d5cb7e759224fea7a279e" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.ow2.asm" name="asm-tree" version="7.0-beta">
<artifact name="asm-tree-7.0-beta.jar">
<sha256 value="a2ec5b55ceb359c324ad48b15e912e33c75889237413976d1505fe32ecde82f2" origin="Generated by Gradle"/>
</artifact>
<artifact name="asm-tree-7.0-beta.pom">
<sha256 value="56e37d6b54903ca842eef8fe6c8863bc7f405186bc43e74a21575a3f2428ba70" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
<artifact name="pcollections-2.1.2.pom">
<sha256 value="207839ab1011448bae3886fc36b6cb9fff1f5b3fa5f10cc79d242cee9dc1c3de" origin="Generated by Gradle"/>
</artifact>
</component>
Upgrade Lombok to support JDK16+ This fixes the IllegalAccessError problem documented at https://stackoverflow.com/a/66981165/622403
2021-11-13 13:43:00 +01:00
<component group="org.projectlombok" name="lombok" version="1.18.22">
<artifact name="lombok-1.18.22.jar">
<sha256 value="ecef1581411d7a82cc04281667ee0bac5d7c0a5aae74cfc38430396c91c31831" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
Upgrade Lombok to support JDK16+ This fixes the IllegalAccessError problem documented at https://stackoverflow.com/a/66981165/622403
2021-11-13 13:43:00 +01:00
<artifact name="lombok-1.18.22.pom">
<sha256 value="6669bd6674aa9e52a2a97344ab3411b31295b2e64c7881e27c2ed6beb66922c2" origin="Generated by Gradle"/>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</artifact>
</component>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<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>
<artifact name="slf4j-api-1.7.30.pom">
<sha256 value="7e0747751e9b67e19dcb5206f04ea22cc03d250c422426402eadd03513f2c314" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.slf4j" name="slf4j-parent" version="1.7.30">
<artifact name="slf4j-parent-1.7.30.pom">
<sha256 value="11647956e48a0c5bfb3ac33f6da7e83f341002b6857efd335a505b687be34b75" origin="Generated by Gradle"/>
</artifact>
</component>
<component group="org.sonatype.forge" name="forge-parent" version="10">
<artifact name="forge-parent-10.pom">
<sha256 value="c14fb9c32b59cc03251f609416db7c0cff01f811edcccb4f6a865d6e7046bd0b" origin="Generated by Gradle"/>
</artifact>
</component>
<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>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01: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>
Update tor-browser to v11.0.15 / tor-binary to v0.4.7.8
2022-07-04 12:04:48 +02:00
<component group="org.vafer" name="jdependency" version="2.1.1">
<artifact name="jdependency-2.1.1.jar">
<sha256 value="642d23a86217850721d9fa80671683d8308fd03114f0da7af553d43b82013a09" origin="Generated by Gradle"/>
</artifact>
<artifact name="jdependency-2.1.1.pom">
<sha256 value="4a139306cbe0aa3765bd9fd837a71253a911a9c4e55c50e062a4bd6843ee19a1" origin="Generated by Gradle"/>
</artifact>
</component>
Migrate to Gradle's built-in dependency verification This commit removes the use of our fork of the gradle-witness plugin in favor of Gradle's relatively new built-in dependency verification feature [1]. The gradle/verification-metadata.xml file was produced using the following command: ./gradlew --write-verification-metadata sha256 build Where `build` is the usual `gradle build` command. All dependency configurations are resolved this way, and written out to the file. The resulting file contains 273 unique dependency declarations, as compared to just 64 in our now-removed gradle-witness.gradle file. This means that the coverage of dependencies verified is much more complete. The new file contains the same sha256 checksums for each dependency as the old file. This was manually spot-checked for a significant number of the dependencies. Like with gradle-witness, builds will break when dependencies are upgraded (and now also when they are added). To fix these breakages, the `--write-verification-metadata sha256` option must be provided to the build. Note that new entries will be added for upgraded depedencies, but old entries are not removed automatically from the file. These must be removed manually. [1]: https://docs.gradle.org/current/userguide/dependency_verification.html
2021-11-13 12:51:41 +01:00
</components>
</verification-metadata>
Reference in New Issue Copy Permalink