Smooth Build is a build tool which provides a functional language which lets you describe a build process in a simple and readable way. A build script for a simple Java program can be as simple as "app.jar: files("src") | javac | jar;" All built artifacts are cached and indexed (hashed) using the sha1 of the expression (function name and its arguments) which returned a given artifact. This way, Smooth never builds the same artifact twice.
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.
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.
RenderConfig allows the definition of a set of modifications that can be used to transform (or render) a set of source files to provide tailored configuration specific to a particular instance of an application. A typical use case for this is where your application requires a set of configuration files that identify multiple servers that provide particular application services. These application servers will differ depending on whether you are running the application in development, testing, or in production. With RenderConfig, at build time you can explicitly produce a set of configuration files that support all of these configurations, providing the ability to ship the configuration with the other build artifacts.
Assimilate is a Maven2 plugin that allows developers to import dependencies from other pre-built Maven projects without a formal parent-child hierarchy existing between the projects. There is no limit to the number of project dependencies. Maven 2.0.9's "import" scope acts not on managed dependencies, but on those declared in the dependency management section of the imported pom file. Assimilate, in contrast, is designed to act on managed dependencies of any prebuilt Maven project (stored in the local repository), as though they were declared in the local project's managed dependency section.
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.
Maven Integration for Eclipse makes it easy to use Maven in Eclipse. Features include: a form-based and XML editor for the Maven POM; a quick search in remote Maven repositories and integration with Nexus Maven repository manager; Maven-based dependency management and automatic downloading of required dependencies and sources; launching Maven from within Eclipse; creating new projects using Maven Archetypes; materializing projects using Maven metadata; integration with JDT, AJDT, and WTP; integration with Maven SCM, Subclipse, Subversive, and Team/CVS; and extension points and API for 3rd party integration.