Subject Log4J
Author Ken Richard
I use Log4J in my own application - so logging enabled for the driver
because the log4j jar is in the classpath. We control log4j through
method calls in our code instead of using a properties file - but the
settings in the file are getting loaded and applied to
my application. This would not be a problem except for the line:

Every time I start my application - I would get exceptions from log4j
that the log folder was missing. I added a line of code to my startup:
new File("log").mkdirs();

But - now my hard drive is becoming littered with folders called "log".

Would you consider removing the default log4j properties file from the