LuaRocks is a deployment and management system for modules in the Lua programming language. It aims to provide facilities for Lua such as those from module systems of other scripting languages, such as Ruby's RubyGems or Perl's CPAN. LuaRocks allows Lua modules to be installed as self-contained packages called "rocks", which also contain version and dependency information.
Launch4j is a cross-platform tool for wrapping Java applications distributed as jars in Windows native executables. The executable can be configured to search for a certain JRE version or use a bundled one, and it's possible to set runtime options, like the initial/max heap size. The wrapper also provides better user experience through an application icon, a native pre-JRE splash screen, a custom process name, and a Java download page in case the appropriate JRE cannot be found. The increase in size of the application is small.
OMake is a build system and scripting language with a similar style and syntax to GNU make but with many additional features, including support for large projects spanning multiple directories, default configuration files simplifying the standard compilation tasks, fast, reliable, automated, scriptable dependency analysis using MD5 digests, built-in support for defining and running autoconfiguration tests, portability, and built-in functions that provide the most common features of programs like grep, sed, and awk. It also provides active filesystem monitoring that restarts builds automatically when source files are modified. A companion command interpreter that can be used interactively is included.
WideStudio is a multi-platform integrated development environment for building windowed event-driven applications. It uses its own independent class libraries. Automatic source code generation is provided by the application builder, which also provides project management and automatic makefile generation. WideStudio can be used to develop applications on Linux, Solaris, and Windows.
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.
Brockman is an information radiator for monitoring Ant builds. It is useful for Agile software teams that practice continuous integration. Brockman consists of an Ant listener written in Java that outputs that status of your build in XML, a Freemarker template that specifies the format of the output XML file, and an AJAX front end that renders the XML file.