Skip to content

Commit 45df39e

Browse files
committed
1. java-tron refactor
a. add common package for base libraries, incluing network, storage, crypto b. add program package for runnable application c. move all core libraries of blockchain to core package 2. add third-party libs, inlcuding grpc, gossip 3. add tron rpcapi module
1 parent 422008e commit 45df39e

File tree

291 files changed

+25141
-3477
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

291 files changed

+25141
-3477
lines changed

.gitignore

+4-1
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,7 @@ doc
2727
# gossip
2828
pernodedata.*
2929
ringstate.*
30-
shareddata.*
30+
shareddata.*
31+
32+
# svn
33+
.svn

CONTRIBUTING.md

+43-43
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,43 @@
1-
# Contributing to java-tron
2-
3-
java-tron is an open source project.
4-
5-
It is the work of contributors. We appreciate your help!
6-
7-
Here are instructions to get you started. They are not perfect, so
8-
please let us know if anything feels wrong or incomplete.
9-
10-
## Contribution guidelines
11-
12-
### Pull requests
13-
14-
First of all, java-tron follows [gitflow workflow](
15-
https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
16-
Please open pull requests to the **develop** branch. Once approved,
17-
we will close the pull request and merge into master branch.
18-
19-
We are always happy to receive pull requests, and do our best to
20-
review them as fast as possible. Not sure if that typo is worth a pull
21-
request? Do it! We would appreciate it.
22-
23-
If your pull request is not accepted on the first try, don't be
24-
discouraged as it can be a possible oversight. Please explain your code as
25-
detailed as possible to make it easier for us to understand.
26-
27-
### Create issues
28-
29-
Any significant improvement should be documented as [a GitHub
30-
issue](https://github.com/tronprotocol/java-tron/issues) before anyone
31-
starts working on it.
32-
33-
When filing an issue, make sure to answer these three questions:
34-
35-
- What did you do?
36-
- What did you expect to see?
37-
- What did you see instead?
38-
39-
### Please check existing issues and docs first!
40-
41-
Please take a moment to check that your bug report or improvement proposal
42-
doesn't already exist. If it does, please add a quick "+1" or "I have this problem too".
43-
This will help prioritize the most common problems and requests.
1+
# Contributing to java-tron
2+
3+
java-tron is an open source project.
4+
5+
It is the work of contributors. We appreciate your help!
6+
7+
Here are instructions to get you started. They are not perfect, so
8+
please let us know if anything feels wrong or incomplete.
9+
10+
## Contribution guidelines
11+
12+
### Pull requests
13+
14+
First of all, java-tron follows [gitflow workflow](
15+
https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow).
16+
Please open pull requests to the **develop** branch. Once approved,
17+
we will close the pull request and merge into master branch.
18+
19+
We are always happy to receive pull requests, and do our best to
20+
review them as fast as possible. Not sure if that typo is worth a pull
21+
request? Do it! We would appreciate it.
22+
23+
If your pull request is not accepted on the first try, don't be
24+
discouraged as it can be a possible oversight. Please explain your code as
25+
detailed as possible to make it easier for us to understand.
26+
27+
### Create issues
28+
29+
Any significant improvement should be documented as [a GitHub
30+
issue](https://github.com/tronprotocol/java-tron/issues) before anyone
31+
starts working on it.
32+
33+
When filing an issue, make sure to answer these three questions:
34+
35+
- What did you do?
36+
- What did you expect to see?
37+
- What did you see instead?
38+
39+
### Please check existing issues and docs first!
40+
41+
Please take a moment to check that your bug report or improvement proposal
42+
doesn't already exist. If it does, please add a quick "+1" or "I have this problem too".
43+
This will help prioritize the most common problems and requests.

0 commit comments

Comments
 (0)