The top of your Rakefile should read: gem "buildr", "1.0.0" require "buildr" require "buildr/xmlbeans.rb" require "buildr/openjpa" require "buildr/javacc" require "buildr/jetty"
This will use the Buildr Gem 1.0.0. I'm guessing right now it reads: require "buildr/lib/buildr" Which tries to run Buildr form the working copy, not the Gem. We (<= me) do that internally to test Buildr changes against Ode, but sometimes it gets committed to SVN accidentally. Assaf On 5/11/07, Paul Brown <[EMAIL PROTECTED]> wrote:
On 5/9/07, Matthieu Riou <[EMAIL PROTECTED]> wrote: > I've just published a RC3 to correct the problem mentioned by Alex. The new > distributions are available here: > I think the vote can resume with these. +0 from me after downloading and trying to build from source. (MacOS X Intel) I'm having issues with buildr as installed via Ruby gems; a snapshot of my environment is attached (installed gems, ruby version, gem version). If we're going to use buildr (which I +1'd) instead of maven, it's got to be bulletproof. Thanks for packaging it in a ZIP that expanded into a directory; some of the distros (axis, smix) were unpacking into the current directory, which was a bit of a pain. -- [EMAIL PROTECTED] http://mult.ifario.us/
