The TorqueBox team fully welcomes all contributors to the project. We have attempted to organize our code and development tools to make it easy for community members to participate as deeply as they desire.
The project tracks bugs, feature-requests, and other issues through the JIRA issue-tracking system at JBoss.org.
To file issues or requests with JIRA, you must have a JBoss Community account. Signing up is easy.
The code is developed as open-source, with a publicly-accessible source-code repository.
All of the code for TorqueBox is open-source under the LGPL. You may checkout the latest code under development at any time.
The primary source repository is located at GitHub, and is obviously using the Git revision-control system.
Using Git and GitHub, it's simple for contributors to fork the code to develop bugfixes or features, and easily integrate their codelines back with the primary codebase, including all attribution and history.
Git is awesome.
You can easily browse the repository.
You may clone a complete copy of the repository using git.
git clone git://github.com/torquebox/torquebox.git
To learn more about how the source is laid out and how to build it see our source guide.
The code is continuously built using our continuous integration service.
Recent incremental builds are available here.
For interim developer releases, when the TorqueBox gems have not been pushed to the official RubyGems repository, the continuous integration server provides a repository matching the latest build. Links to the Gem repository for each successful incremental build are found on the builds page.
More information on how the TorqueBox maven build works can be found on the maven mechanics page.