Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 20 Aug 2014 17:40:26 +0000 (UTC)
From: "Thomas Vandahl (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12711978.1399049170458.4397.1408556426463@arcas>
In-Reply-To: <JIRA.12711978.1399049170458@arcas>
References: <JIRA.12711978.1399049170458@arcas>
Subject: [jira] [Updated] (JCS-122) rework logging?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Vandahl updated JCS-122:
-------------------------------

    Fix Version/s:     (was: jcs-2.0)
                   jcs-2.1

> rework logging?
> ---------------
>
>                 Key: JCS-122
>                 URL: https://issues.apache.org/jira/browse/JCS-122
>             Project: Commons JCS
>          Issue Type: Improvement
>            Reporter: Romain Manni-Bucau
>             Fix For: jcs-2.1
>
>
> currently JCS relies on [logging]
> Would be great to get rid of this dependency.
> Solutions I see:
> 1) use JUL (with extensibility like in http://svn.apache.org/repos/asf/tomee/tomee/trunk/container/openejb-core/src/main/java/org/apache/openejb/log/logger/)
> 2) write a little factory with a jcs.Logger to be able to switch
> Goal is to be able to adapt to frameworks and users. Guess first will be often JUL (TomEE), second SLF4J, [logging]...
> I'm for 1)


--
This message was sent by Atlassian JIRA
(v6.2#6252)