DevelopmentProcess

(This text was originally located at http://www.esw.inesc-id.pt/cgi-bin/moin.cgi/GitHub)

This page provides a quick tutorial on making a release of JVSTM on github.

The general workflow is an adaptation from http://blog.kaltepoth.de/posts/2010/09/06/github-maven-repositories.html

Making a release on GitHub

This has 2 parts:

• Creating and committing the changes for the release
• Updating the maven repository (in gh-pages) with the released jar

For this purpose you should have two local folders in your computer, by default:

1. jvstm (on branch develop)
2. jvstm-pages (on branch gh-pages)

The following sequence of commands creates the next release:

cd jvstm
git checkout develop
mvn release:prepare
mvn release:clean               (just clears temp files)

git co master
git merge --no-ff <version-tag> (the version-tag was created during release:prepare)

git push upstream develop
git push upstream master
git push upstream <version-tag>

mvn clean deploy  (you may want to check the comment on <distributionManagement> tag in pom.xml)

cd ../jvstm-pages
_ignore/update-directory-index.sh
git add maven-repo
git commit -m "Release <version-tag>"  (or you can be creative!)
git push upstream gh-pages

That's it!

This is just an example. Some variations may be used. The main aspects are:

• advance the pom version
• merge the release-tag to master
• publish the updates on GitHub
• deploy the release to jvstm-pages
• generate index.html files on maven-repo
• push the changes on gh-pages to upstream