DASCA
/
WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated instructions how to update version strings.

This commit is contained in:
Achim D. Brucker 2018-10-27 10:50:07 +01:00
parent 8e11e605a4
commit ffd165a7f2
1 changed files with 18 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
README.md
View File

@ -46,19 +46,33 @@ comLogicalhackingArtifactsPassword=<PASSWORD>
### Preparation ### Preparation
Before publishing new artifacts to the artifacts repository, please update the version identifier in Before publishing new artifacts to the artifacts repository, please update the version identifier in the file `build.gradle` by removing the second `SNAPSHOT`
the file `build.gradle` by replacing the second `SNAPSHOT` and updating the `<VERSION>` identifier.
``` gradle ``` gradle
version '1.5.1-SNAPSHOT-DASCA-SNAPSHOT' version '1.5.1-SNAPSHOT-DASCA-<VERSION>-SNAPSHOT'
``` ```
with the version that should be published. Next, tag the new version: with the version that should be published. Next, commit your changes and tag the
new version:
``` gradle ``` gradle
git commit -m "Preparing release of version <VERSION>." build.gradle
git tag -s "<VERSION>" -m "Tagging version <VERSION>." git tag -s "<VERSION>" -m "Tagging version <VERSION>."
``` ```
Finally, mark the development version by appending `-SNAPSHOT`
``` gradle
version '1.5.1-SNAPSHOT-DASCA-<VERSION>-SNAPSHOT'
```
and commit your changes:
``` gradle
git commit -m "Marked development version" build.gradle
```
### Uploading Artifacts ### Uploading Artifacts
Publishing artifacts is as easy as calling Publishing artifacts is as easy as calling