Buildr is a simple and intuitive build system for Java projects. After 10 months of development and a lot of positive feedback, it will be incubated by the Apache Foundation, which will be opening its doors to its first Ruby project.
While some are still fighting to migrate their project from Ant to Maven2, Buildr is making its way. It has been some time since our review of Buildr, "The build system that doesn't suck", and the public feedback has been positive:
Our previous coverage concluded that "We think it would be interesting to see how Maven and Buildr perform head-to-head." With both Maven and Buildr in the Apache Foundation, the competition is open, let's hope it won't end in a family quarrel.
While some are still fighting to migrate their project from Ant to Maven2, Buildr is making its way. It has been some time since our review of Buildr, "The build system that doesn't suck", and the public feedback has been positive:
Buildr is what we're using for this and future projects. There's a lot to be said about Buildr, but for now let's just say that it gives you a hammer to work with; Maven assigns you a construction contractor.
Overall I believe that Buildr is a much more likely to become the defacto ruby build language, than Raven. If simply because of the active community that Raven seems to lack. So if you are up to replacing the trainwreck that is Maven 2 then I would encourage you to look into Buildr.Since our review there have been several new features, such as:
- Support for Hibernate XDoclet and SchemaExport tasks.
- JDepend UI for seeing depenencies across all projects.
- Cobertura test coverage tasks.
- TestNG support.
- Idea project files generation.
- Buildfile created form existing Maven project POM.
- ANTLR support.
Our previous coverage concluded that "We think it would be interesting to see how Maven and Buildr perform head-to-head." With both Maven and Buildr in the Apache Foundation, the competition is open, let's hope it won't end in a family quarrel.