You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/06/11 15:56:00 UTC

[jira] [Updated] (TINKERPOP-1983) Update Log4j to Log4j2

     [ https://issues.apache.org/jira/browse/TINKERPOP-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette updated TINKERPOP-1983:
----------------------------------------
    Affects Version/s: 3.3.3
          Component/s: build-release

Was there a particular problem to solve that required the upgrade? Or was this more of a housekeeping kind of change?

> 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)