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

Tilman Hausherr commented on PDFBOX-4374:
-----------------------------------------

The dependency in the parent is in dependency-management, so my understanding 
is that it is just about getting the correct version when it is used… and 
that's just in preflight test. Anyway, I have removed it now. In a next step 
(after builds on CI have worked) I'll also remove the entry in "Import-Package" 
in the pom files.

> Switch from log4j to slf4j
> --------------------------
>
>                 Key: PDFBOX-4374
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-4374
>             Project: PDFBox
>          Issue Type: Bug
>          Components: Utilities
>            Reporter: Mihai Nita
>            Priority: Critical
>
> 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-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org

Reply via email to