On 1/30/08, xenHalfLife <[EMAIL PROTECTED]> wrote: > > Not trying to start flame war, but why did you guys for the love of god > choose Ruby/Rake as build tool =).
1) We didn't like the verbosity of Ant/Maven1/Maven2; we actually went from 5,443 lines of Maven2 XML over 52 files, into a single build script of 485 lines. 2) We tried really, really hard with Maven2. First, it was hard to do simple things. Second, our build was in constant breakage. 3) We like Ruby; We're not Java zealots and we believe Ruby is the best tool for the job. (Sorry if I borrowed the royal "we" for an instant) On the more serious note do you guys have any plans to perhaps switch build > process to some standard (Maven et al), > I know its the matter of preference but I thought Apache projects are > required to use some standards, including ones > for build process. Buildr is now an Apache project and we hope more projects adopt it because we strongly believe it waaaay better. (Whooops here goes the royalty again!) To have to download Ruby, and to have to learn perhaps another language in > order to develop some kind of build process > plugin that is specific to BPEL/ODE does not seem "pleasent". There's nothing specific to Ode/BPEL in Buildr. If you learn Buildr, you'll be able to use it in other projects and you'll probably save yourself some time and frustration. Not to mention that learning a new language and new tools open horizons... Actually I considered some contributions to ODE but when I saw Ruby > requirement, oo dear, Im out =). Well, you're in luck because we already took care of the build issues so you can concentrate on the Java part. Simply type "buildr eclipse", launch Eclipse and you won't have to use much of Buildr if you don't want to. (Or your favorite IDE) Anyway, ODE seems really good keep up the good work. Thanks :) Let us know if you need any help installing Ruby, Rake, and Buildr. It's real easy. http://incubator.apache.org/buildr/getting_started.html alex
