FitNesse Launcher Maven Plugin can launch FitNesse as a wiki server or automatically run FitNesse tests as part of a standard integration-test/verify build. It allows configuration of FitNesse's classpath through plugin dependencies and injects all Maven project properties as FitNesse variables (which can be overridden from the commandline using "-D").
The maven-buildmetadata-plugin is a Maven 2 plugin that helps you easily add build metadata to generated archive artifacts. When a product is running on an application server, this tool can tell you which version of which artifact is currently running on that server, which artifact maps to which source code version in the SCM repository, what configuration set (including profiles and environment variables) has been used to generate the artifact, on which machine was the artifact built, and when was the artifact built. The provided metadata include SCM information, build time, operating system, Java runtime, Maven execution information, build user, build host name, and build version.
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.
CarrotGarden SCR provides an OSGI Service-Component descriptor generator according to a proposal described in RFC 0172 Declarative Services Annotations. It is comprised of annotations, a Maven plugin, and an Eclipse connector, and allows for interactive SCR component descriptor updates in Eclipse, which are compatible with non-interactive Jenkins Maven builds.
The Maven License Verifier Plugin is a Maven plugin that is intended to check the licenses of artifacts managed by Maven. This can be done during the build process, you can choose to let the build fail if an artifact with a wrong license is used. The licenses are categorized by a definition file that lists them with their different URLs and names. This can be different from project to project.