Changes to the test classpath suggested by Igor worked. I was under the
wrong impression that Wicket Tester was deploying my web app the same way it
is deployed in Tomcat in production and hence was always reading
WEB-INF/classes/log4j.properties.
On Fri, Mar 19, 2010 at 2:11 PM, Igor Vaynberg wro
put another log4j.properties into your src/test/resources or
src/test/java. since the test dirs are before the main dirs when tests
run they will override log4j.properties in your src/main/resources or
src/main/java
-igor
On Fri, Mar 19, 2010 at 12:59 PM, Alec Swan wrote:
> Hi,
>
> It looks like
Hi,
It looks like the link you provided is temporarily down, but I am assuming
that your idea was to replace log4j.properties file with the one specific to
each maven profile.
This is definitely an option, but I am have limited control over the build
file because it is generated by my NetBeans ID
You can look at how I set up configuration stuff in my Advanced Wicket
example code:
http://svn.carmanconsulting.com/public/wicket-advanced/trunk
Basically, I use maven profiles to point to different configuration
directories for each environment (dev, test, prod). Perhaps that
would help.
On F
We have WEB-INF/classes/log4j.properties file which instructs log4j to log
to ${catalina.home}/logs/${logFileName}.log file. This works great when I
deploy the web app in Tomcat.
However, I would like the logs to be written to a different file when I run
my tests that use WicketTester and start th
