chore(cleanup-docs): deleted last-remaining deprecated files and folders

docs/docs/cactus/support.md

@@ -6,7 +6,6 @@ This section contains the ledger supported versions for connectors in Hyperledge
 *   [Besu](support/besu.md)
 *   [Corda](support/corda.md)
 *   [Fabric](support/fabric.md)
-*   [Quorum](support/quorum.md)
 *   [xDai](support/xdai.md)
 *   [Substrate](support/substrate.md)
 

docs/docs/cactus/support/xdai.md

@@ -115,6 +115,6 @@ xDai 1.8.27
 
 
 
-[Previous](quorum.md "Quorum Support") [Next](substrate.md "Substrate Support")
+[Previous](fabric.md "Fabric Support") [Next](substrate.md "Substrate Support")
 
 * * *

docs/docs/weaver/getting-started/enabling-weaver-network/corda.md

@@ -121,10 +121,10 @@ repositories {
   }
 }
 dependencies {
-  implementation(group: 'org.hyperledger.cacti.weaver.sdk.corda', name: 'weaver-sdk-corda', version: "2.0.0-alpha.1")
-  implementation(group: 'org.hyperledger.cacti.weaver.imodule.corda', name: 'interop-contracts', version: "2.0.0-alpha.1")
-  implementation(group: 'org.hyperledger.cacti.weaver.imodule.corda', name: 'interop-workflows', version: "2.0.0-alpha.1")
-  implementation(group: 'org.hyperledger.cacti.weaver.protos', name: 'protos-java-kt', version: "2.0.0-alpha.1")
+  implementation(group: 'org.hyperledger.cacti.weaver.sdk.corda', name: 'weaver-sdk-corda', version: "2.0.0-rc.2")
+  implementation(group: 'org.hyperledger.cacti.weaver.imodule.corda', name: 'interop-contracts', version: "2.0.0-rc.2")
+  implementation(group: 'org.hyperledger.cacti.weaver.imodule.corda', name: 'interop-workflows', version: "2.0.0-rc.2")
+  implementation(group: 'org.hyperledger.cacti.weaver.protos', name: 'protos-java-kt', version: "2.0.0-rc.2")
 }
 ```
 (Or check out the [package website](https://github.com/hyperledger/cacti/packages/1856827) and select a different version.)
@@ -445,7 +445,7 @@ Weaver provides a [pre-built image](https://github.com/hyperledger/cacti/pkgs/co
   RELAY_PORT=<relay-server-port/"port" in config.toml>
   EXTERNAL_NETWORK=<docker-bridge-network>
   DOCKER_IMAGE_NAME=ghcr.io/hyperledger/cacti-weaver-relay-server
-  DOCKER_TAG=2.0.0-alpha.1
+  DOCKER_TAG=2.0.0-rc.2
   ```
     - The `PATH_TO_CONFIG` variable should point to the properties file typically named `config.toml` (you can name this whatever you wish). See further below for instructions to write this file.
     - The `RELAY_NAME` variable specifies a unique name for this relay. It should match what's specified in the `config.toml` (more on that below).
@@ -536,7 +536,7 @@ Weaver provides a [pre-built image](https://github.com/hyperledger/cacti/pkgs/co
   DRIVER_RPC_PASSWORD=<driver-rpc-username>
   EXTERNAL_NETWORK=<docker-bridge-network>
   DOCKER_IMAGE_NAME=ghcr.io/hyperledger/cacti-weaver-driver-corda
-  DOCKER_TAG=2.0.0-alpha.1
+  DOCKER_TAG=2.0.0-rc.2
   RELAY_TLS=<true|false>
   RELAY_TLSCA_TRUST_STORE=<truststore-jks-file-path>
   RELAY_TLSCA_TRUST_STORE_PASSWORD=<truststore-jks-file-password>

docs/docs/weaver/getting-started/enabling-weaver-network/fabric.md

@@ -83,8 +83,8 @@ Below, we list the template functions with sample code that you, as a developer,
   ```go
   require(
       ...
-      github.com/hyperledger/cacti/weaver/common/protos-go/v2 v2.0.0-alpha.1
-      github.com/hyperledger/cacti/weaver/core/network/fabric-interop-cc/libs/assetexchange/v2 v2.0.0-alpha.1
+      github.com/hyperledger/cacti/weaver/common/protos-go/v2 v2.0.0-rc.2
+      github.com/hyperledger/cacti/weaver/core/network/fabric-interop-cc/libs/assetexchange/v2 v2.0.0-rc.2
       ...
   )
   ```
@@ -176,8 +176,8 @@ Below, we list the template functions with sample code that you, as a developer,
   ```go
   require(
       ...
-      github.com/hyperledger/cacti/weaver/common/protos-go/v2 v2.0.0-alpha.1
-      github.com/hyperledger/cacti/weaver/core/network/fabric-interop-cc/interfaces/asset-mgmt/v2 v2.0.0-alpha.1
+      github.com/hyperledger/cacti/weaver/common/protos-go/v2 v2.0.0-rc.2
+      github.com/hyperledger/cacti/weaver/core/network/fabric-interop-cc/interfaces/asset-mgmt/v2 v2.0.0-rc.2
       ...
   )
   ```
@@ -327,7 +327,7 @@ Consider a scenario inspired by the [global trade use case](../../user-stories/g
 
 (In preparation, a suitable access control policy must be recorded on `tradelogisticschannel` in `trade-logistics-network`, and a suitable verification policy must be recorded on `tradefinancechannel` in `trade-finance-network`. We will see how to do this in the "Startup and Boostrap" section later.)
 
-You will need to insert some code in the Layer-2 application that accepts a B/L and submits a `RecordBillOfLading` transaction in `trade-finance-network`. (No code changes need to be made in any application in the other network.) The logic to accept a B/L should be replaced (or you can simply add an alternative) by a call to the `interopFlow` function offered by the [cacti-weaver-sdk-fabric](https://github.com/hyperledger/cacti/pkgs/npm/cacti-weaver-sdk-fabric) library (there's an [equivalent library in Golang](https://github.com/hyperledger/cacti/releases/tag/weaver%2Fsdks%2Ffabric%2Fgo-sdk%2Fv2.0.0-alpha.1) too). The following code sample illustrates this (the Golang equivalent is left to the reader):
+You will need to insert some code in the Layer-2 application that accepts a B/L and submits a `RecordBillOfLading` transaction in `trade-finance-network`. (No code changes need to be made in any application in the other network.) The logic to accept a B/L should be replaced (or you can simply add an alternative) by a call to the `interopFlow` function offered by the [cacti-weaver-sdk-fabric](https://github.com/hyperledger/cacti/pkgs/npm/cacti-weaver-sdk-fabric) library (there's an [equivalent library in Golang](https://github.com/hyperledger/cacti/releases/tag/weaver%2Fsdks%2Ffabric%2Fgo-sdk%2Fv2.0.0-rc.2) too). The following code sample illustrates this (the Golang equivalent is left to the reader):
 ```js
 const ihelper = require('@hyperledger/cacti-weaver-sdk-fabric').InteroperableHelper;
 const interopcc = <handle-to-fabric-interop-chaincode>;   // Use Fabric SDK functions: (new Gateway()).getNetwork(...).getContract(<fabric-interop-chaincode-id>)
@@ -536,7 +536,7 @@ Weaver provides a [pre-built image](https://github.com/hyperledger/cacti/pkgs/co
   RELAY_PORT=<relay-server-port/"port" in config.toml>
   EXTERNAL_NETWORK=<docker-bridge-network>
   DOCKER_IMAGE_NAME=ghcr.io/hyperledger/cacti-weaver-relay-server
-  DOCKER_TAG=2.0.0-alpha.1
+  DOCKER_TAG=2.0.0-rc.2
   ```
     - The `PATH_TO_CONFIG` variable should point to the properties file typically named `config.toml` (you can name this whatever you wish). See further below for instructions to write this file.
     - The `RELAY_NAME` variable specifies a unique name for this relay. It should match what's specified in the `config.toml` (more on that below).
@@ -630,7 +630,7 @@ Weaver provides a [pre-built image](https://github.com/hyperledger/cacti/pkgs/co
   EXTERNAL_NETWORK=<docker-bridge-network>
   TLS_CREDENTIALS_DIR=<dir-with-tls-cert-and-key>
   DOCKER_IMAGE_NAME=ghcr.io/hyperledger/cacti-weaver-driver-fabric
-  DOCKER_TAG=2.0.0-alpha.1
+  DOCKER_TAG=2.0.0-rc.2
   DRIVER_TLS=<true|false>
   DRIVER_TLS_CERT_PATH=path_to_tls_cert_pem_for_driver
   DRIVER_TLS_KEY_PATH=path_to_tls_key_pem_for_driver

weaver/core/network/corda-interop-app/build.gradle

@@ -49,7 +49,7 @@ buildscript {
 plugins {
     id 'java'
     id 'org.jetbrains.dokka' version '0.10.1'
-    id "com.jfrog.artifactory" version "4.16.1"
+    id "com.jfrog.artifactory" version "5.2.3"
     id "maven-publish"
 }