chore: make version more maintainable and change it to 0.1.0 #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
No, it is just the chore before release.
Rationale for this change
The version field is scattered everywhere in the repo. The parent
pom.xml
and its children have their own version, however, in almost every case, they should be identical. Modifying all fields is tedious and error-prone work.What changes are included in this PR?
Apache Maven
, this is easy.Are there any user-facing changes?
Real users are not influenced. Developers of this project should take care of this PR. If you want to change the version field, just modify the property
revision
in parent pom, rather than modify all pom files. It was not convenient to maintain the version field before. Developers would forget to alter the version field in child pom.How does this change test
Pass the existing CI.