You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "David Crossley (JIRA)" <ji...@apache.org> on 2005/09/19 04:23:54 UTC
[jira] Created: (FOR-676) logkit.xconf has no effect on configuration when in commandline mode
logkit.xconf has no effect on configuration when in commandline mode
--------------------------------------------------------------------
Key: FOR-676
URL: http://issues.apache.org/jira/browse/FOR-676
Project: Forrest
Type: Bug
Components: Core operations
Versions: 0.8-dev
Reporter: David Crossley
Fix For: 0.8-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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (FOR-676) logkit.xconf has no effect on
configuration when in commandline mode
Posted by "Tim Williams (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (FOR-676) logkit.xconf has no effect on configuration when in commandline mode
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-676?page=all ]
Ross Gardler updated FOR-676:
-----------------------------
Fix Version: 0.9
(was: 0.8-dev)
Moving to 0.9 - I think it is important that this is fixed soon, but shouldn't be a blocker for 0.8
> logkit.xconf has no effect on configuration when in commandline mode
> --------------------------------------------------------------------
>
> Key: FOR-676
> URL: http://issues.apache.org/jira/browse/FOR-676
> Project: Forrest
> Type: Bug
> Components: Core operations
> Versions: 0.8-dev
> Reporter: David Crossley
> Fix For: 0.9
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (FOR-676) logkit.xconf has no effect on
configuration when in commandline mode
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ 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.