Fix for latest Rails 3-1-stable

[nixme]

I noticed that while active_reload was successfully overloading the regular reload proc, classes were still being cleared after every request (ActionDispatch::Reloader). Turns out run_callbacks(:cleanup) was still executing the old proc because the memoized function wasn't cleared out. So this fix forces recompilation of ActionDispatch::Reloader's cleanup callbacks and everything works again.

Thanks for this library btw, makes a huge difference developing on Rails.

[manuelmeurer]

+1 can we get this merged in?

[paneq]

Sorry that it took me so long to take care of this bug. Unfortunately I cannot reproduce it. It is even tested that after request the constant is still defined https://github.com/paneq/active_reload/blob/master/test/unit/reload_test.rb#L75 which means that code was not reloaded (by the old proc or something). Could you provide more details about what's going wrong? I added few puts statments in my rails code and do not see any difference with and without this line. However #12 issue suggests that there is something going on and I do not know what. I would be glad to here more about the bug and fix it. I tested with rails 3.1 .

[bdimcheff]

@nixme's change made active_reload work with 3.1 for me too. It definitely isn't working for me without it.

[paneq]

I included this fix however I am not happy that no one can provide a test case that would show that active reload works better with this fix in some situations. Maybe in the future...