The JIRA issue tracker:http://jira.codehaus.org/browse/GPARS
The Git repository held at GitHub is the official mainline:
is the official master of the codebase. This is the repository used by continuous integration servers and the one treated as "correct". The To work on the codebase please fork the repository on GitHub in the usual GitHub workflow way. Keeping the master branch as a mirror of the mainline, working on a feature branch and then sending in pull requests based on that feature branch seems to be the best way of working. Please refer to the Git and GitHub documentation for any further details on using Git and GitHub.
A repository that is a mirror of the GitHub repository is maintained at Codehaus in order to continue integration with various continuous integration servers (over time more of this will migrate to GitHub). Also this Codehaus project remains the location of the issue tracker and is the route for artefacts to get into the Maven repository.
You should never need to clone this repository, but for completeness, the command:
git clone git://git.codehaus.org/gpars.git GPars
creates a clone of the repository in the subdirectory GPars. Please refer to the Git documentation for any further details on using Git.The The above URL gives read-only access to the repository (the norm in a DVCS world). Those people with write access to the repository should use the URL:
for their mirror clone instead of the previous one so that they can push new revisions.
Source Repository mirrors
The main repository is mirrored on GitHub to enable easy contribution through personal GitHub branches.
Project commiters and contributors typically keep their personal clones of the main repository for feature branches:
The gradlew script will download and setup gradle for the project and execute the build.
gradlew clean build
In build.gradle and in doc.properties set the version property
version = '0.1112'
Also update the ReleaseNotes.txt file.