Another data point is that if I try to run rake from bundler, I get: mario:(git)radiant[mario-rails3]/$ bundle exec rake -P (in /Users/mario/tmp/radiant/radiant) rake aborted! uninitialized constant Radiant /Users/mario/tmp/radiant/radiant/Rakefile:9:in `<top (required)>' (See full trace by running task with --trace)
So it gets past the require 'dataset/tasks', but blows up on the line that says: Radiant::Application.load_tasks --Mario On Nov 28, 2:05 pm, Mario Aquino <mario.e.aqu...@gmail.com> wrote: > I'd like to do what you suggest and perhaps I am going about it the > wrong way. I thought what you were suggesting below was creating a > local gem build of the radiant rails3 branch and then unpacking that > in a 'lib/radiant' directory within the project I am working in. Is > that what you were suggesting or something different? > > I tried doing what I just described, and I got an error trying to run > rake. Here's what I did: > > mario:(git)radiant[mario-rails3]/$ rake -P | grep gem > rake aborted! > no such file to load -- dataset/tasks > /Users/mario/tmp/radiant/radiant/Rakefile:7 > (See full trace by running task with --trace) > > I had a look in the Rakefile and saw that on line 7, it is trying to > require 'dataset/tasks'. There isn't a dataset directory with a > tasks.rb file anywhere that could find in the project. Do I need to > have something else in place to have the rail3 branch working? I was > hoping that all I needed to do was: rake radiant:gem and have the > local branch built into a gem that I could unpack in my project (per > your suggestion), but it seems that creating a gem from the branch > isn't working out of the box (unless there is another way to do it). > > --Mario > > On Nov 28, 11:15 am, Joshua Danger French <j...@vitamin-j.com> wrote: > > > > > On Nov 27, 2010, at 5:34 PM, Mario Aquino wrote: > > > > Since I am trying to use Radiant as a Rails engine, what should the > > > RADIANT_ROOT be? Should I freeze the radiant gem (and put it under > > > vendor/gems)? > > > Radiant as an engine is still under construction and I can't recommend > > using it for anything real at the moment. The 0.9.1 gem is only compatible > > with Rails 2, but that's the latest stable release. > > > For hacking on the rails3 branch, I've been unpacking it into lib/radiant > > and pointing Bundler there with gem "radiant", :path => "lib/radiant".
