Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Received-SPF: pass (athena.apache.org: domain of hedhman@gmail.com designates
 209.85.223.177 as permitted sender)
MIME-Version: 1.0
Sender: hedhman@gmail.com
From: Niclas Hedhman <niclas@hedhman.org>
Date: Tue, 31 Mar 2015 01:25:25 +0800
Message-ID: 
 <CADmm+KfpFcohj=1R=qTD7DeA4OD2mVcULDboJ7LrgiJDV68mBA@mail.gmail.com>
Subject: Discuss; SLF4J in Core
To: Qi4j Dev <dev@zest.apache.org>
Content-Type: multipart/alternative; boundary=089e0158a9babe5023051284c5ef

--089e0158a9babe5023051284c5ef
Content-Type: text/plain; charset=UTF-8

Although codebase is not imported to Apache Zest yet, I am looking at
removing the SLF4J dependency in Core.


As the first step, I want to remove the current logging that is in Core,
simply because it is scattered and primarily in place to support a couple
of development efforts in the past and not really useful to the user of
QI4j.

Second step is to provide a similar extension mechanism for Logging as for
Metrics, and if people plugin a Logging provider, then that will be used.

Third step is to migrate the LIbraries and other Extensions to use this SPI
mechanism.

Fourth step; Look into "useful" logging from Core, that make sense to users.

WDYT?


Cheers
-- 
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java

--089e0158a9babe5023051284c5ef--