You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2019. It is now read-only.
The latest version of Bundler 1.0.0.rc.4 doesn't appear to have a from_gemfile method.
This is being called from the my_engine/engine.rb file inside the my_engine.require_dependencies initializer.
Not being the bundler expert I'm not really sure how to solve the problem, but the engineer "rails g my_engine:install" method from inside the host does not work without it.
The text was updated successfully, but these errors were encountered:
As a work around, you can comment out that initializer, and instead maintain your list of dependencies within the gemspec block inside your Rakefile (a la jeweler.)
I know maintaining two lists is annoying, but it should get you by while I take a look.
When I start the host application and visit a route in my engine the stylesheet and javascript links that get created inside the engine all have the appropriate ASSET_PREFIX appended to them like they should and everything works great.
But, when I reload the page (without restarting the server) any subsequent page view is missing the ASSET_PREFIX which of course causes all the necessary javascript and stylesheets to look in /javascripts, etc instead of /my_engine/javascripts like it should.
I am running rails 3.0.0-rc (although I have also tried with the latest rails master code with the same results).
Any insight into how to fix this would be greatly appreciated.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The latest version of Bundler 1.0.0.rc.4 doesn't appear to have a from_gemfile method.
This is being called from the my_engine/engine.rb file inside the my_engine.require_dependencies initializer.
Not being the bundler expert I'm not really sure how to solve the problem, but the engineer "rails g my_engine:install" method from inside the host does not work without it.
The text was updated successfully, but these errors were encountered: