You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/03/17 17:44:00 UTC

[jira] [Commented] (BEAM-14069) Traces of Log4j 1.x inside of beam-runners-flink-1.13-job-server-2.36.0.jar

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

Kenneth Knowles commented on BEAM-14069:
----------------------------------------

Sounds like a transitive dependency uses log4j 1.x

I don't think it is possible. for Beam to adjust all transitive dependencies. Do you have an example of a specific problem this has caused you? Maybe we can address the issue somehow. Otherwise I think it is infeasible.

> Traces of Log4j 1.x inside of beam-runners-flink-1.13-job-server-2.36.0.jar 
> ----------------------------------------------------------------------------
>
>                 Key: BEAM-14069
>                 URL: https://issues.apache.org/jira/browse/BEAM-14069
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>    Affects Versions: 2.36.0
>            Reporter: Ohad Pinchevsky
>            Priority: P2
>
> Log4j 1.x is EOL, still traces of it found inside beam-runners-flink-1.13-job-server-2.36.0.jar
> Path to pom.xml with that version:
> /beam-runners-flink-1.13-job-server-2.36.0/META-INF/maven/log4j/log4j/pom.xml
> Inside version tag: 1.2.17
>  



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