So I'm starting on a new idea I had today, and figured now would be as best time as ever to jump back on edge.
The first hiccup I ran in to was almost immediate. Rails assumes you have ActiveResource, yet doesn't provide it when you freeze edge.
`gem_original_require': no such file to load -- active_resource
So make sure the SECOND thing you do after freezing edge is:
svn export http://dev.rubyonrails.org/svn/rails/trunk/activeresource vendor/rails/activeresource
Popularity: 4% [?]
About
Mmm, Del.icio.us
You could also just run the freeze task again; it will pick it up. :)
Oh, nice, thanks.
I don't get this. Every time I use rails it bites me in the ass and I always end right back at this blog post. Why don't they just fix this? Why does active_resource always get excluded?
jc: Because it's the Rails 1.2.x rails:freeze:edge task that's checking out the frameworks on the first run. When you run the command the second time it's Rails Edge's rails:freeze:edge, which knows that active_resource needs to be "frozen" as well. (Yes, I know, it's been a couple of months...)