[
http://jira.magnolia-cms.com/browse/MAGNOLIA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20080#action_20080
]
Hudson CI server commented on MAGNOLIA-1760:
--------------------------------------------
Integrated in !http://hudson.magnolia-cms.com/nocacheImages/16x16/blue.gif!
[magnolia_main-trunk
#387|http://hudson.magnolia-cms.com/job/magnolia_main-trunk/387/]
* capitalized log messages (+ some cleanup)
* made loggers private static final (except for ObservedManager)
* removed loggers from subclasses of ObservedManager for consistency
> Review default log configuration
> --------------------------------
>
> Key: MAGNOLIA-1760
> URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1760
> Project: Magnolia
> Issue Type: Improvement
> Components: build, core
> Reporter: Gregory Joseph
> Assignee: Gregory Joseph
> Fix For: 4.0
>
>
> We should review and simplify the default log4j configuration shipped with
> Magnolia. At the moment it logs in different files under
> MAGNOLIA_HOME/WEB-INF/logs, AND to catalina.out (or whatever container's
> default log file is), which is confusing. It seems people tend to look at the
> former when asked for logs, and those are mostly irrelevant in case of
> problems.
> We should
> - simplify the configuration (I'd tend to use a single file)
> - provide (commented out or in a separate config file to be renamed) easy
> ways to get more logging for typical problematic cases
> Also consider MAGNOLIA-18 and other log related issues.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
