[
https://issues.apache.org/jira/browse/HADOOP-16206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378469#comment-17378469
]
Steve Loughran commented on HADOOP-16206:
-----------------------------------------
do it in trunk. It'll complicate the life of those who backport stuff from 3.4
to 3.3, or into internal builds, but that can't hold things back forever.
We can get the changes in trunk, let them stabilise, then worry about what to
do after that. backporting to branch-3.3 for a switch in 3.3.2 is going to
create tension, even if we make the case "this was a transient dependency and
our rules give us a get out clause there"
> Migrate from Log4j1 to Log4j2
> -----------------------------
>
> Key: HADOOP-16206
> URL: https://issues.apache.org/jira/browse/HADOOP-16206
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.3.0
> Reporter: Akira Ajisaka
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HADOOP-16206-wip.001.patch
>
>
> This sub-task is to remove log4j1 dependency and add log4j2 dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
