[
https://issues.apache.org/jira/browse/FOR-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780343#action_12780343
]
Tim Williams commented on FOR-676:
----------------------------------
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
> 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.
