Scarab is a highly customizable artifact tracking system supporting the following feature set:
All aspects of your artefact management can be defined on a per Module basis so that each of your modules is configured for your specific tracking requirements.
There are two types of downloads. There is the source download available from the Subversion repository and the stable releases from the Project Download List.
You can also download a nightly built of the trunk from here.
If you want to actively contribute, give feedback or send bug fixes, then please join the Scarab.Tigris.org community by registering with the site and then requesting an Observer role within the Scarab project.
To get involved with the development of Scarab, please join the developer's mailing list.
The first thing you should send when you join the list is to post an introduction message that tells the group:
The first place to start off with developing on Scarab is to download the SVN tree and explore the documentation, build system and code that is there already. Build a "target" sandbox, startup Tomcat and explore the templates that are already there. Analyze the database design and look at the files in the src/sql directory (the default-data and sample-data) files are very helpful. The README.txt file documents everything necessary to get a Scarab installation up and running. It's easy.
After searching the issue tracker and you really do have an original problem to report, then please report it using our issue tracker. Register and create a new account. Make sure to request a DEVELOPER role. Please include a detailed message that describes the problem (make it as easy as possible to understand), how to reproduce the problem and a stack trace if one is generated. Make sure the the email address you register with is subscribed to the issues mailing list so that emails generated by Scarab are properly sent to the mailing list.
NOTE: Please do not use the issue tracker to create test issues. You can use our runbox hosted by Saxess to create as many test issues as you want.
If the issue tracker is unavailable or you have a problem with it, please contact the developers and let them know.