The Cube42Logger was developed before Log4J came
into power. Its time now to get it on mainstream with
the rest of the world.
A study into the Cube42Logger and Log4J needs to be
conducted and then report to Matt ideas and
suggestions on how to proceed with this. Once a
decision is made new task will be issued.
One thing to keep in mind is that the Cube42Logger does
have features that will be missed. For one its integrated
into the rest of the system. So the concept of
subsystems is preserved throughout it. Another is that
it is possible to just shut off debug, or error without
shutting off the rest.
It may be that Log4J should not be used with the
Cube42Logger because it does not keep enough of the
features needed.
One suggested Idea.
Cube42Logger works off of a class called logger that is
specified in a file what logger to use. This allows the
Logger to be swapped out for other implementations.
One idea is to create a new Cube42Logger that uses
Log4J. That was we could keep the type safety of the
Cube42Logger but, pick up all the advantages of the
Log4JLogging system.
