On Sat, Dec 26, 2009 at 11:52 AM, Peter Schröder p...@blau.de wrote:
hi alex,
most of the problems i get around are actually examples from the
documentation!
Understood and I'm very thankful you bring these up. Buggy documentation
is often worse than buggy code.
i (and all the people i
Hi Buildr folks,
My ultimate goal in adopting a Java build system is to have a
single-command process that can check code out of source control,
build it, and deploy it. Now that I've read through all the Buildr
documentation, it seems that Buildr is perfect for building, and I
also think it can
Hi Will,
The code checkout step is usually handed by the continuous integration
server, such as Hudson, Luntbuild/Quickbuild, Bamboo, etc. It conveniently
avoids the bootstraping issue of having Buildr run before a buildfile is
available.
If this is too heavy for you, I'd consider using Rake or
Thanks, Alex. I know what I want to accomplish, but I'm still getting
a feel for the Java ecosystem, so I'm not always sure what the popular
steps are along the way. Your pointers toward fresh research material
are very helpful.
-- Will