|
|
|
Download | JavaDocs | Source | Wiki |IRC | IRC Log | Mailing Lists | Discussion Forum | Support |
There are many ways you can help make Jencks a better piece of software - please dive in and help!
Try surf the documentation - if somethings confusing or not clear, let us know. 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 jencks? Try surfing the our issue tracker for open issues or features that need to be implemented, take ownership of an issue and try fix it.
If you'd rather a more gentle introduction to working on the jencks project, how about you try look at the unit tests cases and help us to improve our test coverage.
Getting in touch
There are various ways of communicating with the jencks community.
- subscribe to the Mailing Lists and take part in any conversations
- pop by on IRC and say hi
- add some comments to the wiki
If you find a bug or problem
Please raise a new issue in our issue tracker
If you can create a JUnit test case then your issue is more likely to be resolved quicker.
e.g. take a look at some of the existing unit tests cases
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.
Submitting patches
We gladly accept patches if you can find ways to improve, tune or fix jencks 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
diff -u Main.java.orig Main.java >> patchfile.txt
or
cvs diff -u Main.java >> patchfile.txt
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 jencks-developers on the issue tracker. To join the group, please mail the dev@jencks.codehaus.org mail list with the email address you used to register with the issue tracker and we'll add you to the group.
Why not dive in and try tackle some of our outstanding issues?
Error rendering macro: java.io.IOException: Error on line 1: Content is not allowed in prolog. rssoutput-1168142532.txt
[ edit ]