You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@marmotta.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/11/28 20:38:35 UTC

[jira] [Commented] (MARMOTTA-390) Implement Logging Configuration

    [ https://issues.apache.org/jira/browse/MARMOTTA-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13835043#comment-13835043 ] 

ASF subversion and git services commented on MARMOTTA-390:
----------------------------------------------------------

Commit 7b9cb5a1b532b5691eacb019c410a4020683816b in branch refs/heads/develop from [~wastl]
[ https://git-wip-us.apache.org/repos/asf?p=marmotta.git;h=7b9cb5a ]

base infrastructure for MARMOTTA-390 (configurable logging) functional


> Implement Logging Configuration
> -------------------------------
>
>                 Key: MARMOTTA-390
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-390
>             Project: Marmotta
>          Issue Type: New Feature
>          Components: Platform
>            Reporter: Sebastian Schaffert
>            Assignee: Sebastian Schaffert
>
> Changing the logging configuration currently is a mess and therefore people are not using logging properly. We should have a nice user interface to configure the logging service based on different components. Perhaps each module could provide information about which modules it offers for logging and which packages are associated with it, and then the administrator can change the logging level easily for each component in a configuration interface.



--
This message was sent by Atlassian JIRA
(v6.1#6144)