[
https://issues.apache.org/jira/browse/TINKERPOP-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563721#comment-16563721
]
Florian Hockmann commented on TINKERPOP-1983:
---------------------------------------------
First, thanks for the link. Configuring Logback is probably a good solution for
most users.
I still think that we should try to not depend on a library that isn't
maintained anymore. But if it's not feasible to update this dependency right
now because Spark and Hadoop still use it in that version, then I'm ok to close
the ticket for now and we can reconsider later when those two projects updated
to a newer version of log4j.
> Update Log4j to Log4j2
> ----------------------
>
> Key: TINKERPOP-1983
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1983
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.3.3
> Reporter: Florian Hockmann
> Priority: Minor
>
> TinkerPop uses Log4j version 1.2.17 but Log4j 1 reached end of life almost
> three years ago:
> {quote}On August 5, 2015 the Logging Services Project Management Committee
> announced that Log4j 1.x had reached end of life.
> {quote}
> Source: [http://logging.apache.org/log4j/1.2/]
> It would be great if we could update to Log4j2 as it brings some nice
> benefits like new logging layouts for example (one of them is the JSON layout
> which is very useful to have to collect logs in something like the ELK stack
> or Graylog).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
