Just put your log4j.properties into src/test/resources. This way the
config file will be on the classpath of the dev environment and is not
shipped inside the war. In production put the config file into the
container.
18.02.2010, в 19:13, Everton Agner <everton_ag...@yahoo.com.br>
написал(а):
Hi,
There is any T5 Elegant way so I can automatically switch between
distincts Log4J configurations related to Development/Production
Mode? We have the @Symbol "productionMode", so I believe there is
some way I can achieve that using this information...
I saw something like that on an old Struts 1.3 application, so there
was a log4j.properties file on the project and, on the Deployment
Server, other log4j.properties (and some weird conf to make it
works). So, I could work on DEBUG mode on the Development
environment, and in ERROR mode on Deployment environment without
having to change.
I don't want to do that here, though...
Any help would be appreciated.
Thanks!
Everton
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
