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.
RTK (Ruckus Tool Kit) is a high-performance, Perl-based, dynamic, content-generation system. It provides a nearly transparent bridge between HTML-based code pages and traditional CGI-based systems. It has been designed to automatically take advantage of existing systems, such as basic CGI, Apache's mod_perl, FastCGI, and SpeedyCGI, but does not require such systems for high-performance optimization.
POSIX amake is a software build tool that adds automatic dependency analysis and target caching to GNU Make. It monitors and records commands executed, programs executed, shared libraries opened, files accessed, and environment-variable values. It maintains a multiuser/multihost cache of previously built targets: an SQL database stores target metadata (e.g., command and dependency checksums), while a regular filesystem stores target files and their siblings. The target-cache feature is optional, being enabled by a makefile variable. It has been used to build and rebuild the Linux kernel.
Minimac is a minimalist, general purpose text macro processor. Its simplicity should make it particularly well suited as a front end preprocessor for little language compilers. It is meant to be simpler to use than m4. It uses an explicit argument stack, and user functions are defined by concatenation (similar to the Forth language). Macro expansion is delayed to the last possible moment. The software is currently in alpha release.
FitNesse Maven Classpath Plugin is a Maven2 plugin that collects the dependencies of the entire project, including its sub-modules. After resolving the artifacts, it generates the classpath and inserts it into the Fitnesse test suites, thus solving the problem of maintaining the correct classpath in FitNesse.