try not to hardcode log4j configurations
Sunday, September 2nd, 2007Around work, I've seen applications where there are several log4j configurations checked in along side each other(dev, test, prod). Often, the only differences are location of where the log files go. A better solution would not require, .war files to be re-built in order to only change log file destinations. Log4J will interpret variables given to ...