I am using Log4j 2.0 in a Web Application, which is packaged as a .war
file, and deployed in an application server.
I want to bundle a default Log4j configuration within the .war file, but
make it possible to override it in the application server when deploying,
without tampering with the .war
That isn’t really feasible currently. Once Log4j finds the configuration file
it can poll the file’s timestamp to see if it was updated and reload it, but
IMO it would not be a great idea to modify the log4j config file in the
directory wherever Jetty deployed it, and it certainly would be
