You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -147,7 +147,7 @@ We would like all developers to follow a standard development flow and coding st
147
147
2. Review the code before submission.
148
148
3. Run standardized tests.
149
149
150
-
`Sonar`-scanner and `Travis CI` continuous integration scanner will be automatically triggered when a pull request has been submitted. When a PR passes all the checks, the **java-tron** maintainers will then review the PR and offer feedback and modifications when necessary. Once adopted, the PR will be closed and merged into the `develop` branch.
150
+
`Sonar`-scanner and CI checks (GitHub Actions) will be automatically triggered when a pull request has been submitted. When a PR passes all the checks, the **java-tron** maintainers will then review the PR and offer feedback and modifications when necessary. Once adopted, the PR will be closed and merged into the `develop` branch.
151
151
152
152
We are glad to receive your pull requests and will try our best to review them as soon as we can. Any pull request is welcome, even if it is for a typo.
153
153
@@ -161,7 +161,7 @@ Please make sure your submission meets the following code style:
161
161
- The code must have passed the Sonar scanner test.
162
162
- The code has to be pulled from the `develop` branch.
163
163
- The commit message should start with a verb, whose initial should not be capitalized.
164
-
- The commit message should be less than 50 characters in length.
164
+
- The commit message title should be between 10 and 72 characters in length.
165
165
166
166
167
167
@@ -196,7 +196,7 @@ The message header is a single line that contains succinct description of the ch
196
196
The `scope` can be anything specifying place of the commit change. For example: `framework`, `api`, `tvm`, `db`, `net`. For a full list of scopes, see [Type and Scope Reference](#type-and-scope-reference). You can use `*` if there isn't a more fitting scope.
197
197
198
198
The subject contains a succinct description of the change:
199
-
1. Limit the subject line, which briefly describes the purpose of the commit, to 50 characters.
199
+
1. Limit the subject line, which briefly describes the purpose of the commit, to 72 characters (minimum 10).
200
200
2. Start with a verb and use first-person present-tense (e.g., use "change" instead of "changed" or "changes").
Copy file name to clipboardExpand all lines: docs/implement-a-customized-actuator-en.md
+38-31Lines changed: 38 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,13 +36,19 @@ message Transaction {
36
36
AccountCreateContract = 0;
37
37
TransferContract = 1;
38
38
........
39
-
SumContract = 52;
39
+
SumContract = 60;
40
40
}
41
41
...
42
42
}
43
43
```
44
44
45
-
Then register a function to ensure that gRPC can receive and identify the requests of this contract. Currently, gRPC protocols are all defined in `src/main/protos/api/api.proto`. To add an `InvokeSum` interface in Wallet Service:
45
+
Then register a function to ensure that gRPC can receive and identify the requests of this contract. Currently, gRPC protocols are all defined in `src/main/protos/api/api.proto`. First add the import for the new proto file at the top of `api.proto`:
46
+
47
+
```protobuf
48
+
import "core/contract/math_contract.proto";
49
+
```
50
+
51
+
Then add an `InvokeSum` interface in the Wallet service:
46
52
47
53
```protobuf
48
54
service Wallet {
@@ -60,13 +66,11 @@ service Wallet {
60
66
```
61
67
At last, recompile the modified proto files. Compiling the java-tron project directly will compile the proto files as well, `protoc` command is also supported.
62
68
63
-
*Currently, java-tron uses protoc v3.4.0. Please keep the same version when compiling by `protoc` command.*
64
-
65
69
```shell
66
-
# recommended
70
+
# recommended — also recompiles proto files automatically
67
71
./gradlew build -x test
68
72
69
-
# or build via protoc
73
+
# or build via protoc (ensure the protoc version matches the one declared in build.gradle)
@@ -78,7 +82,11 @@ After compilation, the corresponding .class under the java_out directory will be
78
82
79
83
For now, the default Actuator supported by java-tron is located in `org.tron.core.actuator`. Creating `SumActuator` under this directory:
80
84
85
+
> **Note**: The Actuator must be placed in the `org.tron.core.actuator` package. At node startup, `TransactionRegister.registerActuator()` uses reflection to scan that package and auto-discovers every `AbstractActuator` subclass. Each subclass is instantiated once (triggering the `super()` constructor which calls `TransactionFactory.register()`), so no manual registration code is needed.
Copy file name to clipboardExpand all lines: docs/modular-deployment-en.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# How to deploy java-tron after modularization
2
2
3
-
After modularization, java-tron is launched via shell script instead of typing command: `java -jar FullNode.jar`.
3
+
After modularization, the recommended way to launch java-tron is via the shell script generated in `bin/`. The classic `java -jar FullNode.jar` command is still fully supported as an alternative.
4
4
5
-
*`java -jar FullNode.jar` still works, but will be deprecated in future*.
5
+
> **Supported platforms**: Linux and macOS. Windows is not supported.
6
6
7
7
## Download
8
8
@@ -29,7 +29,7 @@ After unzip, two directories will be generated in java-tron: `bin` and `lib`, sh
29
29
30
30
## Startup
31
31
32
-
Use the corresponding script to start java-tron according to the OS type, use `*.bat` on Windows, Linux demo is as below:
32
+
Use the shell script to start java-tron (Linux / macOS):
0 commit comments