QDox is a high speed, small footprint parser for extracting class/interface/method definitions from source files complete with JavaDoc @tags. It is designed to be used by active code generators or documentation tools.

XPlanner is a project planning and tracking tool for eXtreme Programming (XP) teams. If you are not familiar with XP software development practices, the links page contains pointers to relevant resources. To summarize the XP planning process, the customers pick the features to be added (user stories) to each development iteration (typically, one to three weeks in duration). The developers estimate the effort to complete the stories either at the story level or by decomposing the story into tasks and estimating those. Information about team development velocity from the previous iteration is used to estimate if the team can complete the stories proposed by the customer. If the team appears to be overcommitted, the set of stories are renegotiated with the customer. The XPlanner tool was created to support this process and address issues experienced in a long-term real-life XP project.

JTestMe dynamically defines smoke test suites for Java applications - dramatically improving the continuous integration cycle time. When running your full test suite (unit, integration, functional, etc), the code is instrumented by JTestMe to record any application Classes which are executed are recorded into a repository. Super-classes and classes that are not directly called by tests are also included so the full scope is captured. When you change any application code, the repository is inspected to determine which tests should be run. These tests can then be run whenever you save a file, as an automatic pre-commit build test suite, or as an automatic smoke test suite for a Continuous Integration tool like CruiseControl. Rather than having to run the whole test suite again, or pre-defined test suites, only the tests that need to be run to exercise the changed code are the ones that are run, dramatically reducing the feedback cycle for most applications. Once the smoke test suite has passed, you would then run the full test suite, in order to fully assure the behaviour of the application (as some changes are beyond the view of the executing code). Maturity: Alpha (currently working, test-driven code) Dependencies: * AspectJ * Java 1.5