logkit.xconf has no effect on configuration when in commandline mode

• Key: FOR-676
• Type: Bug
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: David Crossley
• Component/s: Core operations
• Affects Version/s: 0.8
• Fix Version/s: 0.9-dev

Description

Raising loglevels in main/webapp/WEB-INF/logkit.xconf has no effect when doing 'forrest'. All okay when doing 'forrest run'.

Comments

[Ross Gardler]

Moving to 0.9 - I think it is important that this is fixed soon, but shouldn't be a blocker for 0.8

[Tim Williams]

David, can we get more details? I can't seem to reproduce it. I've done the following:
//verified that logkit is setup to ERROR for lm
cd test-site
forrest seed-sample
forrest site
//look in /build/webapp/WEB-INF/logs/locationmap.log and only see ERROR's
change logkit moving lm to DEBUG
forrest site //again, same site
//look again at /build/webapp/WEB-INF/logs/locationmap.log and now see tons of DEBUG's

This is what I gather from the issue at least, am I missing something? I'm hoping a fix would be a simple as adding the config to the classpath for that target or something but I can't recreate it.

Thanks,
--tim

[David Crossley]

I think that it is fixed. Doing 'svn log' shows that i did quite a bit of fine-tuning of logkit.xconf since this issue. So somthing must have fixed it.

My original test was more general:
- <category name="core" log-level="WARN">
+ <category name="core" log-level="DEBUG">

Now that works in both forrest modes, so closing.