[
https://issues.apache.org/jira/browse/AMQ-8472?focusedWorklogId=725127&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-725127
]
ASF GitHub Bot logged work on AMQ-8472:
---------------------------------------
Author: ASF GitHub Bot
Created on: 11/Feb/22 13:33
Start Date: 11/Feb/22 13:33
Worklog Time Spent: 10m
Work Description: cshannon commented on pull request #766:
URL: https://github.com/apache/activemq/pull/766#issuecomment-1036218508
@jbonofre - So @gemmellr and I have been talking and this might have
already been correct. The issue is apparently the Zookeeper dependencies (and
linkedin) have a hard dependency on log4j so it sounds like if someone wants to
use this module they actually do need a compile time dependency on reload4j so
that it gets pulled in and doesn't break. Robbie can comment as well but I
think maybe we just leave it as it already was? It's gone in 5.17.0 anyways
Even if we don't make this change at least we can pull in the license file
changes (updated years) and re-cut the release since it got cancelled already.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 725127)
Time Spent: 5.5h (was: 5h 20m)
> Switch to reload4j for logging
> ------------------------------
>
> Key: AMQ-8472
> URL: https://issues.apache.org/jira/browse/AMQ-8472
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.16.4
>
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> This task is to switch AMQ 5.16.x to use Reload4J instead of Log4J for
> logging. That way we get fixes for the various CVEs in Log4J 1.x, until AMQ
> picks up Log4J 2.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
