SBuild is a Scala-based build system. It features platform independence, multi project support, automatic detection of needed actions, automatic up-to-date detection, a flexible scheme handler mechanism, Maven repository support, Ant task integration, automatic cross-project resolving of dependencies, high speed, a simple "syntax" that requires almost no Scala knowledge, behind-the-sceens compilation of build script to bytecode for fast execution time, and built-in scheme handlers for HTTP and Maven.
crumb is an experimental build-automation program to provide functionality similar to "make" but with a much better approach, where dependencies for all invocations are automatically detected, by using shared-library level hooks. The spawned processes are also paused if a missing dependency needs to be generated. Oddly, with parallelism, this means that the linker might run before the compiler, but it will get paused until the compiler is done generating the input that it needs. Another purpose of crumb is to provide users with absolutely minimal build description files. This means that the build description files need to be smaller than an equivalent shell script containing the commands that would have built the project directly.
Lattice is a Java build system with strong multi-module support. Build files are written not in XML, but in the Python language. The benefits are much better readability and powerful imperative build scripting. For multi-module projects, Lattice uses topological sorting to decide the correct order to build each module. Because a custom task is just a regular Python function, they can perform any type of work, including invoking other Java build systems such as Ant, Maven, or Ivy.
EBuild is a software project build, dependency management, and reporting technology. The aim is to be able to tackle any build problem in a structured, declarative, and elegant way. It is written in Java, but can be used to build all manner of projects and is extensible via a plugin interface. It is best compared to something like Maven (and in some respects Ivy). It aims to overcome certain design flaws and the resultant unnecessary complexity. The EBuild build model is general, but plugins need to be written in a JVM compatible language. Existing plugins all deal with the Java ecosystem, so EBuild is most suitable for Java and mixed technology software projects.