Tim Connor

Whereas having an outdated dependency installed without specifying it in config.gems will not kill rake outright, but will crash rake gems at the point in it's ...

The generalized problem is having a gem both as a dependency and specified on it's own will crash rake gems out, if you have an older version of the gem install...

It's not just frozen gems. If you have gruff installed, for instance, it will require rmagick. If you specify a newer version of rmagick (for whatever reason) i...

There is still a "already activated version x.y" problem in the gem loading. If you have a frozen gem with unfrozen dependencies (for instance if the dependency...

No rush, I just noticed today that it actually did work right with dev mode reloading, on my set-up, despite bitsweat saying something about it not.

You probabl...

fyi, this does NOT break reloading for me with metal in dev mode, in fact it fixes it.

Not sure if this is the right solutions (didn't see where to put any tests for the rack level stuff), but this solves the problem for me:

http://github.com/tim...

Metals aren't handles by the usual dependency handling of rails, since they are manually required in Rails::Rack::Metal

if metal = all_metals[requested_metal...

So as per the discussion on 4a3afe0b what do you think a good solution is, Josh?

+1 to any reasonably intelligent refactoring out of special cases in AR