if you supply none the default will be
log4j.properties / log4j.xml
regards,
Peter
- Original Message -
From: "Igor Drobiazko"
To: "Tapestry users"
Sent: Friday, 19 February, 2010 10:10:50 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: [T5.1] Log4j a
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
написал(а):
Hi,
There is any T5
Hi Everton, I usually do this kind of things (Properties that change between
environments) using maven profiles + and maven resource filtering as
explained here:
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
It's not a Tapestry way but u could find it useful.
On Thu
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 Str
