You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Tilman Hausherr (JIRA)" <ji...@apache.org> on 2018/11/10 06:43:00 UTC
[jira] [Assigned] (PDFBOX-4374) Switch from log4j to slf4j
[ https://issues.apache.org/jira/browse/PDFBOX-4374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tilman Hausherr reassigned PDFBOX-4374:
---------------------------------------
Assignee: Tilman Hausherr
> Switch from log4j to slf4j
> --------------------------
>
> Key: PDFBOX-4374
> URL: https://issues.apache.org/jira/browse/PDFBOX-4374
> Project: PDFBox
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 2.0.12, 3.0.2 JBIG2
> Reporter: Mihai Nita
> Assignee: Tilman Hausherr
> Priority: Minor
> Fix For: 2.0.13, 3.0.0 PDFBox
>
>
> Hello,
> I would be nice to use slf4j instead of relying explicitly on log4j. ([slf4j.org|http://slf4j.org])
> There are adapters from slf4j to many logger implementations, one of them is log4j.
> The decision of which log engine does not belong in a library, it belongs to the user of that library.
> This was apparently done already by several Apache projects. Searching for slf4j in Jira shows Zookeeper, HBase, HDFS, Parquet, Cloudstack, Nemo, EmpireDB, Oozie, Hadoop, and many others.
>
> I can offer a patch, I have done such migration before.
> Thank you very much,
> Mihai
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org