Here is describe how to make release and publish release artefacts.
x.y.z
where:
Following guide is useful when new minor or major change should be released. Guide suppose releasing version x.y.0.
git status
git checkout -b rel-x.y
Now all further operations will be done in rel-x.y branch.
mvn versions:set -DnewVersion=x.y.0
mvn clean package
Verify release binaries. Release files could be found at places:
mvn versions:commit
git add --all git commit -m "rel-x.y.0" git push
TODO add guide when branch x.y.2 already exists and version x.y.3 should be released.
Documentation is stored at github in extra branch called gh-pages. To publish new version of documentation it's enough to commit it to gh-pages branch. It could be donein a few easy steps.
In your home directory is file ~/.m2/settings.xml. If file doesn't exist crate new one. Edit server section:
<servers>
...
<server>
<id>github</id>
<username>user</username>
<password>s!cr!t</password>
</server>
...
</servers>This setting provide user name and password for github account.
mvn clean site-deploy
Than after few minutes new site version should be uploaded at https://jajir.github.io/microcol/.