-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app.require throwing errors for core library #12
Comments
Did you ever figure this out? |
Nope, I stopped using the class instead :( Moved on to more pressing problems unfortunately. But I still would love to solve this one. |
Guys i also struck with the same problem!! anyone solved this... i'm also trying!! |
+1 |
For routing... main_app.require should do the trick. |
Routing? |
What's that Sent from my iPhone
|
Same problem; getting the following :
ruby-2.0.0-p353 |
anyone with a solution for this issue? |
Here another person trying to use set |
Hi-
I've been tearing my hair out trying to figure this out. I added MotionBundler to my project, and now see it compiling stuff in the
group :motion
category of my Gemfile. However, when I try to add a core ruby class ("set" in my case) toMotionBundler.setup do |app| app.require
it fails.Here is my sample rakefile snip:
And the error I get is:
Any help would be most appreciated. I'm using this by the book, and "set" is a core class in Ruby... so this seems very odd.
The text was updated successfully, but these errors were encountered: