[
https://issues.apache.org/jira/browse/FOR-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Crossley closed FOR-676.
------------------------------
Resolution: Fixed
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.
> logkit.xconf has no effect on configuration when in commandline mode
> --------------------------------------------------------------------
>
> Key: FOR-676
> URL: https://issues.apache.org/jira/browse/FOR-676
> Project: Forrest
> Issue Type: Bug
> Components: Core operations
> Affects Versions: 0.8
> Reporter: David Crossley
> Fix For: 0.9-dev
>
>
> Raising loglevels in main/webapp/WEB-INF/logkit.xconf has no effect when
> doing 'forrest'. All okay when doing 'forrest run'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
