Unexplained superflulous space is disturbing my feng shui
Resque.logger accessor
Initial Resque::Logger module

This module can be selectively included in classes which wish to take
advantage of the centralized logging facilities, enabling a set of 5
methods for each severity level (debug, info, warn, error, fatal)
Log Resque::Worker through Resque::Logger

This change includes Resque::Logger, a set of wrappers around the
underlying Resque.logger, into Resque::Worker, sending all logging
through that as opposed to just printing it to STDOUT.

Some notes on this change:

* Users can now configure any stdlib Logger duck type they want to do
  their logging. By default it uses Logger.new(STDOUT)

* Resque::Worker.verbose and .very_verbose are presently noops. They
  should probably be deprecated in lieu of setting a severity threshold
  on the logger itself (i.e. Logger::INFO vs Logger::DEBUG). That said,
  they could be made backwards compatible and set the severity level
  automatically (hopefully we'd still deprecate them anyway).

* Testing is made easier by the fact that logging can be intercepted as
  opposed to having to use "capture_io" to make assertions about what is
  being logged or not o_O

* Kernel#warn is now intercepted in classes that include Resque::Logger
  and directed to the log as opposed to STDERR. This may or may not be
  desirable.

* I deleted some tests (which might be a bad idea):
  - "very verbose works in the afternoon" hardcoded the timestamp
    format. I'm going to guess stdlib Logger works in the afternoon
  - There were tests for "displays warning when not using term_child"
    which were using capture_io. Uncertain about the importance of
    displaying this warning and given the wonky nature of the tests, I
    just deleted them for now. I can potentially add them back if they
    were important.
Oops, forgot to check in log/.gitignore
MiniTest fixups for Ruby 1.8
master has no platform guard, so why should we?
Use MiniTest's built in after-test hooks

In 2fa18ac I made the following change:

-require 'test/unit'
+require 'minitest/unit'

This had the unintended consequence of running the test suite twice!
(Even weirder, that *only* happened on 1.9.2 and JRuby in 1.9 mode o_O)

Since the tests don't presently clean up after themselves or initialize
Redis into a clean state, this broke the build because the second test
run would fail.

Tenderlove recommened replacing the existing wonky at_exit handler with
a proper MiniTest::Unit.after_test hook and it fixed the problem. Plus
it's waaaay less wonky ;)
Rename Resque::Logger to Resque::Logging

Having both Resque.logger (which expects and stdlib Logger duck type)
and Resque::Logger is confusing.

Resque::Logging is a module that can be added to any class that wants
logging functionality. Giving it a slightly different name helps
disambiguate.

In addition, this gets rid of Resque::Logging#__log__ in favor of a
class method. Boo underscore methods!
Print a deprecation warning for verbose and very_verbose

This changes the accessor methods for Resque::Worker#verbose and
very_verbose to no ops that print a deprecation warning with
instructions on how to change the severity level.

Hopefully this will help ease the transition for anyone presently
relying on these flags.
Include caller info with the deprecation warning
add very verbose test back
remove module_function on logger module
Support the old verbose/very_verbose logging

implement this as Logger formatters on top of stdlib's Logger.
You must specify the Logger first before setting verbose/very_verbose
set a default logger when a Worker is created
add the term child warn tests back
Revert "remove module_function on logger module"

This reverts commit d3ae69f286712ef363097c4bddc251b3f29a96e1.
make Worker#log / Worker#log! available for backwards compat
only setup logger in resque.rb
deprecation warning for using verbose/very_verbose