You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pdfbox.apache.org by le...@apache.org on 2024/01/02 10:24:21 UTC

(pdfbox-docs) branch master updated: PDFBOX-5695: document the swithc to Log4j on website

This is an automated email from the ASF dual-hosted git repository.

lehmi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pdfbox-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new bcdaad92 PDFBOX-5695: document the swithc to Log4j on website
bcdaad92 is described below

commit bcdaad9256b452d8bf39f520b2a1c39ec66da7aa
Author: Andreas Lehmkühler <an...@lehmi.de>
AuthorDate: Tue Jan 2 11:23:44 2024 +0100

    PDFBOX-5695: document the swithc to Log4j on website
---
 content/4.0/migration.md | 23 +++++++++++++++++------
 1 file changed, 17 insertions(+), 6 deletions(-)

diff --git a/content/4.0/migration.md b/content/4.0/migration.md
index 72c73306..74afd5ca 100644
--- a/content/4.0/migration.md
+++ b/content/4.0/migration.md
@@ -40,18 +40,17 @@ PDFBox 4.0 requires at least Java 11. Testing has been done up to Java 20.
 
 All libraries on which PDFBox depends are updated to their latest stable versions:
 
-- Bouncy Castle 1.75
-- Apache Commons Logging 1.2
-- picocli 4.7.4
+- Bouncy Castle 1.77
+- Apache Log4j 2.22.1
+- picocli 4.7.5
 
 For test support the libraries are updated to
 
-- JUnit 5.10.0
+- JUnit 5.10.1
 - JAI Image Core 1.4.0
 - JAI JPEG2000 1.4.0
 - Apache JBIG ImageIO Plugin 3.0.4
-- Apache Commons IO 2.13
-- Apache Log4j 2.20.0
+- Apache Commons IO 2.15.0
 
 ## General Changes for PDFBox 4.0
 
@@ -64,3 +63,15 @@ was still limited to PDF/A 1B.
 
 People looking for an open source preflight solution might check [VeraPDF](https://verapdf.org/). The VeraPDF parser is based on a PDFBox fork and
 was stream lined to fit their needs. But VeraPDF is still using the PDFBox parser as possible alternative.
+
+### Switch to Apache Log4j
+
+Apache Commons Logging was replaced by Apache Log4j, some of the obvious reasons were
+
+- maintainabilty and performance
+- flexibility
+- JPMS support
+- lambda logging support
+
+[PDFBOX-5695](https://issues.apache.org/jira/browse/PDFBOX-5695) provides more details about the reasons and the transition itself.
+