This project is archived and is in readonly mode.
Initializers aren't run on gem dependency failure
Reported by Ben Sandofsky | August 13th, 2008 @ 03:49 AM | in 2.x
If you don't have a gem you've added to config.gem, your server starts with a warning, but your config/initializers/*.rb files aren't run. It looks like your after_initialize block isn't run, either.
If your app should refuse to run on a missing gem, that's fine, but you should throw an exception. Personally, I'm fine with the current behavior, where you just get a warning. However, the current behavior makes no sense and it's a pain to troubleshoot.
I've also included a test for the initializers folder behavior, since I couldn't find an existing test anywhere.
Comments and changes to this ticket
-
josh November 22nd, 2008 @ 07:34 PM
- State changed from “new” to “wontfix”
I'd have to double check with Rick, but there was a good reason to add that check in.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Ben Sandofsky
josh
Attachments
Referenced by
-
824
Make Gem Dependency Optional
And by THAT I mean #814.