[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    [jira] [Closed] (JSPF-105) Rely on slf4j-api for logging
From:       "Benoit Tellier (Jira)" <server-dev () james ! apache ! org>
Date:       2019-09-30 7:46:00
Message-ID: JIRA.13258220.1569212926000.76200.1569829560194 () Atlassian ! JIRA
[Download RAW message or body]


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

Benoit Tellier closed JSPF-105.
-------------------------------
    Fix Version/s: 1.0.2
       Resolution: Fixed

https://github.com/apache/james-jspf/pull/9 solved this

> Rely on slf4j-api for logging
> -----------------------------
> 
> Key: JSPF-105
> URL: https://issues.apache.org/jira/browse/JSPF-105
> Project: James jSPF
> Issue Type: Improvement
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 1.0.2
> 
> Time Spent: 3h 50m
> Remaining Estimate: 0h
> 
> By using a modern logging API, we can:
> - Avoid the Logger frontend API which:
> - Makes using JSPF easier
> - Reduces code size
> - Avoid forcing the Log4J dependency (that is later excluded in James)
> - Allow using placeholders
> - Remove the need of Logger wiring
> - Allow more precise logs: the classname the log is emmited from is then explicitly \
> used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]