Added support for custom versionFile name, instead of static version.… #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Removed dependency on java-ordered-properties-1.0.2 to java-ordered-properties-1.0.4
|
I saw your changes, most of things were applied in 2.0.3 to clean the code and support latest syntax for Gradle plugins. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
in different scenarios we might need to have different numbering schemes, basically sometimes we deliver internal builds to QA and then we have release builds. We need to keep the build numbers separate, so that we can track the QA build numbers increment in a separate way from the release build numbers.
For that the patch supports setting an alternative version file instead of the version.properties file. That way we can increment each build number independently.