Hey, Sure, no problem for the help. Feel free to subscribe to the buildr user mailing-list [1] and ask questions, we'll surely answer. The buildr documentation [2] is fairly good with lots of examples, so a quick look will probably give you a better idea of how it works and what build scripts look like. If you want to see what a script for a *very* complex build would be, the Apache ODE one is also a good reference [3]. In your case I'm guessing the longest part will be to list the dependencies :)
We now have a fairly good amount of native tasks for external tools support, like XDoclet, XMLBeans or Eclipse project files and for everything else existing Ant tasks can be reused. So you shouldn't hit any show stopper. Cheers, Matthieu [1] [EMAIL PROTECTED] [2] http://incubator.apache.org/buildr/ [3] http://svn.apache.org/repos/asf/ode/trunk/Rakefile On Nov 25, 2007 6:27 PM, Carl Trieloff <[EMAIL PROTECTED]> wrote: > > Copied Matthieu from builder onto the thread. Matthieu, it looks like we > might > look into builder -- any support in answering questions is appreciated > while > we work out if it is the way to go > > Carl. > > > Robert Greig wrote: > > On 23/11/2007, Carl Trieloff <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote: > > > I am fine moving back to ant... consuming maven is a nightmare. every > time you > turn around there is a new set of dependencies. The builder guys at > apachecon > also have an alternative and would help us convert it we wanted to go > that way. > > > I have not tried buildr yet but I did speak to a colleague who is a > Ruby developer and he says that Rake (upon which Buildr is based) is > very good - flexible and straightforward to use. I think the key > requirement is flexibility. > > So I would certainly support closer examination of it, and if it turns > out that it is too immature or otherwise unsuitable we did have an > excellent ant-based system that served us well in the past, courtesy > of Rafi. > > RG > > > >
