1. Quick Start
  2. Installing and Running
  3. Projects
  4. Building
  5. Artifacts
  6. Packaging
  7. Testing
  8. Settings & Profiles
  9. Languages
  10. More Stuff
  11. Extending Buildr
  12. Contributing

Copyright 2007-2016 Apache Buildr

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Daniel Spiewak:

If you think about it, the question isn’t “Why use Buildr?”, it’s really “Why use anything else?” The advantages afforded by Buildr are so substantial, I really can’t see myself going with any other tool, at least not when I have a choice.

Tristan Juricek:

That’s still the strongest sell: it builds everything I need, and as I’ve needed more, I just got things working without a lot of fuss.

Matthieu Riou:

We used to rely on Ant, with a fairly extensive set of scripts. It worked but was expensive to maintain. The biggest mistake afterward was to migrate to Maven2. I could write pages of rants explaining all the problems we ran into and we still ended up with thousands of lines of XML.

Martin Grotzke:

The positive side effect for me as a java user is that I learn a little ruby, and that’s easy but lots of fun… :-)