Reporting Issues

Submitting bug reports and suggesting new features are important tasks to help improve the quality and functionality of the software. By following the advice given on this page you can help to ensure that all relevant information is captured and entered into the issue tracking system in the correct way. This helps the project team and other contributors to take action in the shortest possible time.

Submitting Bug Reports

When submitting a bug report, please include the following information:

  • The operating system you are using, e.g. RHEL 5, Windows XP, Solaris 10
  • The JDK or JRE you are using, e.g. Sun Microsystems JDK 1.5.0_09
  • As much of the stack trace (if there is one) as necessary to show the cause of the problem.
  • A list of steps needed to reproduce the bug.

The objective is to give enough information for someone with no prior knowledge of the bug to recreate the problem for themselves. Too little information may prevent them understanding when the bug occurs and too much information can create unnecessary confusion.

Submitting Feature Requests

When submitting a request for a new feature make sure to keep it as brief and to the point as possible. Each new feature requires its own issue in the issue tracking system so that they can be addressed separately by developers. It is up to the project leads to determine when new features are added, according to the development plans they have made. You may point out reasons why features should be added sooner rather than later, such as the ability to compete with an alternative technology, but unless you are willing to do the work yourself you may have to wait for development to take place.

Using the Issue Tracking System

Our issue tracking system is available on You may use your user account to login this system. To find out how to use the issue tracking system, refer to the instructions available online.