Message-ID: <1352485241.4809.1394529274288.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4808_1929072000.1394529274288" ------=_Part_4808_1929072000.1394529274288 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The sources of the Groovy project are hosted on Github: = https://github.com/groovy/groovy-core
Additionally, the sources are mirrored on Codehaus' own Git infrastructu=
re as well: http://git.codehaus.org/gitweb.=
You can learn about the repository details = on the Xircles Codehaus admin interface: http://xircles.codehaus.org/projects/groovy/repo/git/repo
If you're interested in contribu= ting, you can send us GitHub pull requests, or submit patches through JIRA.= Please see our contribution page<= /a> for more.
You can also get the sources for each releases in the form of a zip arch= ive. Please head to our download secti= on to download those source packages.
First of all, you'll need to have Git installed on your machine, whether= through the support of your IDE, or as a command-line tool.
If you want to checkout the source code of Groovy, there are three diffe= rent URLs you can use. From the command-line, you can use the command:
You can checkout different branches, in particular:
masteris the latest Groovy branch, for the upcoming major= version
GROOVY_1_8_Xis the branch of the curret Groovy 1.8.x vers= ions (current stable version)
GROOVY_1_7_Xis the branch for the previous official versi= on of Groovy 1.7.x
For fetching a branch the first time, simply use:
To checkout a particular branch:=20 =20 =20
Use the commit command to commit your changes locally:
Say you have committed your changes on
master and want to m=
erge a particular comming on
GROOVY_1_8_X, you can procede as =
To see what's the status of your source tree, you can call:
And if you want to see all the latest commits that you have locally, you= can do:
To retrieve the changes that have been pushed to the server, you can do:=
Of more explicitely:
The various commits you've made are done locally, now is the time to sha= re them with the world by pushing your changes to your Github clone, or to = a publicly available Git repository:
If you're a Groovy despot, you can also push your changes to Codehaus fo= r manual synchronization purpose. But for that, first, you'll have to have = configured an additional remote with:
Then you can push the changes back to GitHub as well:
To push a local branch to the Codehaus Git repository or on the GitHub m= irror, you can do the following:
Contributors might bring their contributions in the form of "pull r=
equests" on our GitHub mirror.
Groovy despots can merge the pull= requests on GitHub through the web interface by following this proposed wo= rkflow:
If you want to learn more about Git, there are many available resources = online, such as: