You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/02/04 14:54:00 UTC

[jira] [Work logged] (AMQ-8472) Switch to reload4j for logging

     [ https://issues.apache.org/jira/browse/AMQ-8472?focusedWorklogId=720916&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-720916 ]

ASF GitHub Bot logged work on AMQ-8472:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Feb/22 14:53
            Start Date: 04/Feb/22 14:53
    Worklog Time Spent: 10m 
      Work Description: jbonofre commented on pull request #754:
URL: https://github.com/apache/activemq/pull/754#issuecomment-1030060198


   While Jenkins is running a build, I'm doing a local build and tests.


-- 
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: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 720916)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: Colm O hEigeartaigh
>            Priority: Major
>             Fix For: 5.16.4
>
>          Time Spent: 10m
>  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)