[
https://issues.apache.org/jira/browse/TINKERPOP-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508271#comment-16508271
]
stephen mallette commented on TINKERPOP-1983:
---------------------------------------------
ok - i was just wondering. thanks for the explanation.
> My understanding of logging in Java was that Logback defines the interface
> and Log4j is the implementation that could be replaced by any other
> implementation of Logback.
Technically, its slf4j defining the interface and then you can replace the
implementation with what you want. I sense that it shouldn't be impossible, but
it's not going to be as easy as just bumping the version number. I think this
change would have to occur in a breaking release because we bundle log4j with
the console/server (i think) and thus someone might depend on that. For
standard maven dependencies I believe the slf4j implementation is up to the
user as it should be so nothing should be a problem there. I also think that
certain tests rely on log4j, so if the API changes by 2.x then those would have
to be dealt with. Finally, i guess if there were changes to any of the log4j
config files then those would need update too.
> 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)
