[
https://issues.apache.org/jira/browse/MXNET-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16644232#comment-16644232
]
Andrew Ayres commented on MXNET-1077:
-------------------------------------
There is a good chance that this will be as simple as changing the version
number in our pom file. Whoever does this should clear their local maven repo
before rebuilding/testing then check the repo after to make sure only the new
log4j version is present.
> Update Scala/Java API bindings to log4j v2.11
> ---------------------------------------------
>
> Key: MXNET-1077
> URL: https://issues.apache.org/jira/browse/MXNET-1077
> Project: Apache MXNet
> Issue Type: Story
> Components: Apache MXNet Scala API
> Reporter: Denis Davydenko
> Priority: Major
>
> Update log4j version used in Java/Scala bindings from v1.2.17 to 2.11
> ([https://search.maven.org/artifact/org.apache.logging.log4j/log4j/2.11.1/pom).]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
