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 IDE. I wonder if there is a way to specify log4j.properties location programmatically in the test code. Maybe somehow override the classpath of Wicket Tester's servlet container? Thanks. Alec On Fri, Mar 19, 2010 at 1:17 PM, James Carman <[email protected]>wrote: > 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 Fri, Mar 19, 2010 at 3:01 PM, Alec Swan <[email protected]> wrote: > > 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 their own servlet containers. > How > > can I instruct my tests to log to a different location or even use a > > different log4j.properties file altogether? > > > > Thanks. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
