Monday, March 31, 2014
I've added another engine. Again it runs just fine as a stand alone application (test/dummy) and as an engine inside the main application, but this time when I use cucumber it mangles the route. The generated controller name is NamespaceController, instead of Namespace::Controller.
The only significant difference between the various engines is that each time I create a new engine I get different versions of various gems like childprocess, docile, and jquery_rails. Am I getting incompatible versions of these gems? If so, how do I control this when I create a new engine?
The only significant difference between the various engines is that each time I create a new engine I get different versions of various gems like childprocess, docile, and jquery_rails. Am I getting incompatible versions of these gems? If so, how do I control this when I create a new engine?
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/d1cced05-d80b-4c3c-a70e-b2ffad49074c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment