There are many ways you can help make Groovy a better piece of software - and we can use all the help we can get Please dive in and help!
Try surfing the documentation - if something is confusing or not clear, let us know - or better still fix it for us . All of this website is maintained in a wiki, so please go right ahead and fix things if they are wrong or contribute new documentation.
Download the code & try it out and see what you think. Browse the source code.
Got an itch to scratch, want to tune some operation or add some feature?
Want to do some hacking on Groovy? Try surfing the our
If you'd rather a more gentle introduction to coding on the Groovy project, how about you try look at the
h2 Getting in touch
There are various ways of communicating with the Groovy community.
- subscribe to the Error rendering macro 'link' : Link needs a name and a URL as arguments.and take part in any conversations
- pop by on Error rendering macro 'link' : Link needs a name and a URL as arguments.and say hi
- add some comments to the Error rendering macro 'link' : Link needs a name and a URL as arguments.
- blog about it and hopefully folks are subscribed to your blog
h2 If you find a bug or problem
Please raise a new issue in our
If you can create a JUnit test case (either via Groovy or Java code) then your issue is more likely to be resolved quicker.
e.g. take a look at some of the
Then we can add your issue to CVS and then we'll know when its really fixed and
we can ensure that the problem stays fixed in future releases.
h2 Submitting patches
We gladly accept patches if you can find ways to improve, tune or fix Groovy in some way.
Most IDEs can create nice patches now very easily. If you're a command line person try the following to create the patch
Once you've created a patch the best way to submit it is to raise a new issue in the issue tracker (see below) and maybe send us a mail on the developer list letting us know about the patch.
h2 Using the issue tracker
Before you can raise an issue in the issue tracker you need to register with it. This is quick & painless.
If you want to have a go at fixing an issue you need to be in the list of groovy-developers on the issue tracker.To join the group, please mail the groovy-dev mail list with the email address you used to register with the issue tracker and we'll add you to the group.