tomykaira/clockwork — pull request #3 by hoverlover (2011-11-10 21:50:54+00:00)
Title: No longer including Clockwork module in clockwork executable

This was causing problems because it puts all the classes, including the `Clockwork::Event` class at the top level. I have an AR model called `Event`, and it was causing a superclass mismatch error. The problem didn't show up in development, I guess because the classes are lazily loaded. But in production, it requires all of the classes up front and that's when the error became apparent.

I updated the README to reflect the changes necessary to run clockwork. Since the `Clockwork` module is no longer included at the top level, a person will need to either qualify the methods with `Clockwork::`, or put them in a `Clockwork` module. The README now reflects both ways.