You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Srikrishna Erra (Jira)" <ji...@apache.org> on 2022/02/01 05:51:00 UTC

[jira] [Commented] (AMQ-7426) Upgrade to log4j2

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

Srikrishna Erra commented on AMQ-7426:
--------------------------------------

Hi [~jbonofre],

   Is there a plan on including this fix in 5.16.x release?

Also, I see there is a plan of releasing 5.17.0 in Feb with this Fix. Are we still on track for releasing 5.17.0 in Feb. Will there be any change to this?

Please let me know.

Thanks,

Srikishna Erra.

> Upgrade to log4j2
> -----------------
>
>                 Key: AMQ-7426
>                 URL: https://issues.apache.org/jira/browse/AMQ-7426
>             Project: ActiveMQ
>          Issue Type: Task
>          Components: Broker
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.17.0
>
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.20.1#820001)