[
https://issues.apache.org/jira/browse/PDFBOX-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17778934#comment-17778934
]
Axel Howind edited comment on PDFBOX-5705 at 10/24/23 5:10 AM:
---------------------------------------------------------------
[~tilman] Hi, I just saw that this has been merged into 3.0, but bot into
trunk. Can you apply to trunk to, or should I include the change in PDFBOX-5695?
was (Author: axh):
Hi, I just saw that this has been merged into 3.0, but bot into trunk. Can you
apply to trunk to, or should I include the change in PDFBOX-5695?
> update log4j dependency to 2.21.0
> ---------------------------------
>
> Key: PDFBOX-5705
> URL: https://issues.apache.org/jira/browse/PDFBOX-5705
> Project: PDFBox
> Issue Type: Improvement
> Affects Versions: 3.0.0 PDFBox
> Reporter: Axel Howind
> Assignee: Tilman Hausherr
> Priority: Minor
> Fix For: 3.0.1 PDFBox
>
> Attachments: update_log4j_to_2_21_0.patch
>
>
> Log4J was updated to version 2.21.0. Just updating the dependency leads to a
> failure when building with Jenkins. This has been discussed on the mailing
> list.
> Currently PDFBox uses Log4J only when running tests and examples. The
> codebase uses commons-logging. When executing tests, logs are rerouted to
> log4j using the jcl-log4j bridge implementation.
> PDFBox has to implementations of the commons-logging LogFactory on the
> classpath. After updating, the original commons-logging implementation is
> chosen.
> This patch updates log4j to version to 2.21.0 and adds a
> commons-logging.properties file for tests and examples that tells
> commons-logging to use the bridge implementation instead of the original one.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
