Simple Continuous Integration Tools (scit) is an automated build and or test system consisting of a set of Perl and expect scripts utilizing common tools that are available for most Unix-like operating systems. The intention is to keep it lightweight while still providing a full set of features. The current version has a command-line and an HTML user interface. It should be possible to make it run on very modest hardware; part of the development and testing has been done on a Nokia N900 phone with both master and slave roles running on the same unit.
Kundo provides a structured, convention based approach for Java builds. Kundo has a pluggable, extensible architecture; it harnesses the power and flexibility of Groovy and Ant to provide a highly configurable Java build framework. Kundo achieves this flexibility with a plug-in architecture that attaches behaviors (provided by Kundo plug-ins) to build lifecycle phases. Kundo consists of a kernel and a set of foundation plug-ins. The kernel is responsible for the orchestration of the multiple collaborators within the build system.
TeamCity is an out-of-the-box build management and continuous integration server supporting both Java and .NET teams. Its unique features include pre-tested commits that — protect the code base and ensures that no broken code is ever committed, a Build Grid that allows builds and tests to be run under different platforms and environments simultaneously, extreme ease of configuration, and integration with top IDEs: Eclipse, IntelliJ IDEA, and Visual Studio.
Architecture Rules is a Java library that allows a programmer to assert code's architecture via unit tests or ant tasks. This test is able to assert that specific packages do not depend on others and is able to check for and report on cyclic dependencies among your project's packages and classes. This project wraps a industry accepted JDepend to simplify the process of maintaining a solid software architecture.
Thunderbolt is a middleware infrastructure suite that includes connectors, Java development libraries, a business process design GUI, and a system monitor GUI. It is appropriate for both telco and financial services. It provides the basis for a simple, efficient integration infrastructure which can be easily extended. While maintaining a SOA in mind, it can easily orchestrate Web services and legacy systems. It's also useful for developing proof of concept projects requiring processing in real time, batch, or both.
JCite makes it possible to cite snippets of Java source code in your HTML documents (API documentation, for instance). The snippets are copied out of Java class source files, which should be part of the regular build. This guarantees that the cited snippets are always up-to-date. If you cite from unit tests, you even get the guarantee that they still work correctly. Finally, thanks to the excellent Java2Html library, the cited snippets get automatic syntax highlighting.
Component Templates for Assets and Artifacts is an Eclipse-based toolkit that allows developers to focus on business aspects of the development process instead of the technological. This Java-implemented toolkit automatically enforces all template-defined constraints, which makes it easier to create ready-to-use and reusable assets or artifacts.
JChav is a way to see the change in performance of your Web application over time by running a benchmark test for each build you produce. It is an Ant task that, when used in conjunction with the JMeter ant task, produces historic views of the performance of your application. Charts are produced for individaul pages of the application along with summary data. If integrated with cruise-control or similar build tools, you will get an idea if the changes you are making to your Web application are improving or degrading performance.