[
https://issues.apache.org/jira/browse/EAGLE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292990#comment-15292990
]
ASF GitHub Bot commented on EAGLE-300:
--------------------------------------
Github user anyway1021 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/192#issuecomment-220544582
No, I didn't put rootLogger into INFO level arbitrarily. The reason is:
1. not all DEBUG messages are useless, sometimes meaningful DEBUG msg could
benefit debugging ERRORs, we can just get rid of DEBUG log dumping, only keep
DEBUG message that we're interested of, such as eagle's.
2. this way of ignoring messy DEBUG msg is just to let spring and
apache-commons components log above INFO level by default, separated from
rootLogger's DEBUG so that we will have more flexible controls on logs of
different components.
Does these make sense?
> Disable spring debug log by default in webservice
> -------------------------------------------------
>
> Key: EAGLE-300
> URL: https://issues.apache.org/jira/browse/EAGLE-300
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.4.0, v0.3.1
> Reporter: Michael Wu
> Assignee: Michael Wu
> Fix For: v0.4.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
