Skip to content

developer-guide.md

Latest commit

 

History

History
157 lines (109 loc) · 4.24 KB

developer-guide.md

File metadata and controls

157 lines (109 loc) · 4.24 KB

JVM

JDK 17 is required. The Temurin builds of Eclipse Adoptium are strongly recommended.

Setup

Note that the below ./gradlew commands should be run from the root of the project.

This project uses the Hiero Gradle Conventions Gradle setup. More details on how to work with the project can be found in the documentation.

Building

./gradlew assemble

Unit Tests

./gradlew :sdk:test

Integration Tests

The tests are only executed if the configuration is provided. That's why we need to pass the configuration file at the beginning of the command.

Using Gradle properties

OPERATOR_ID, OPERATOR_KEY and HEDERA_NETWORK must be passed as Gradle properties (-P parameters).
HEDERA_NETWORK can be set to localhost, testnet or previewnet.

./gradlew :sdk:testIntegration -POPERATOR_ID="<shard.realm.num>" -POPERATOR_KEY="<PrivateKey>" -PHEDERA_NETWORK="<network>"

Using configuration file

./gradlew :sdk:testIntegration -PCONFIG_FILE="<ConfigurationFilePath>"

An example configuration file can be found in the repo here: sdk/src/test/resources/client-config-with-operator.json

Running against the local network

The format of the configuration file should be as follows:

{
    "network": {
        "0.0.3": "127.0.0.1:50211"
    },
    "mirrorNetwork": [
        "127.0.0.1:5600"
    ],
    "operator": {
        "accountId": "0.0.1022",
        "privateKey": "0xa608e2130a0a3cb34f86e757303c862bee353d9ab77ba4387ec084f881d420d4"
    }
}

Running against remote networks

The format of the configuration file should be as follows:

{
    "network": "testnet",
    "operator": {
        "accountId": "0.0.7",
        "privateKey": "d5d37..."
    }
}

HEDERA_NETWORK can be set to testnet, previewnet or mainnet.

Running individual test classes or functions

Running test class:

./gradlew :sdk:testIntegration -POPERATOR_ID="<shard.realm.num>" -POPERATOR_KEY="<PrivateKey>" -PHEDERA_NETWORK="testnet" --tests "<TestClass>"

Running test function:

./gradlew :sdk:testIntegration -POPERATOR_ID="<shard.realm.num>" -POPERATOR_KEY="<PrivateKey>" -PHEDERA_NETWORK="testnet" --tests "<TestClass.functionName>"

Running with Intellij IDEA

  1. Create a new Gradle run configuration (easiest way is to run test class or individual test function from the IDE).
  2. Update "Run" configuration to pass the required Gradle properties (OPERATOR_ID, OPERATOR_KEY and HEDERA_NETWORK).

Managing dependencies

This project uses a combination of Java Modules (JPMS) and Gradle to define and manage dependencies to 3rd party libraries. In this structure, dependencies of the SDK are defined in sdk/src/main/java/module-info.java (which is mirrored in sdk-full/src/main/java/module-info.java). Running ./gradlew qualityGate contains a dependency scope check that makes sure that both files are in sync. Versions of 3rd party dependencies are defined in hiero-dependency-versions/build.gradle.kts. More details about how to add/modify dependencies are found in the Hiero Gradle Conventions documentation on Defining modules and dependencies.

Maintaining generated files

Note that the below ./gradlew commands should be run from the root of the project.

Updating unit tests snapshots

./gradlew updateSnapshots

Updating proto files

./gradlew updateSnapshots

Updating address books

Update all address books:

./gradlew examples:updateAddressbooks

Update address books only for a mainnet:

./gradlew examples:updateAddressbooksMainnet

Update address books only for a testnet:

./gradlew examples:updateAddressbooksTestnet

Update address books only for a previewnet:

./gradlew examples:updateAddressbooksPreviewnet