[
https://issues.apache.org/jira/browse/OPENJPA-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241427#comment-17241427
]
ASF subversion and git services commented on OPENJPA-2842:
----------------------------------------------------------
Commit 61b30777d4e83646325006175f918d9fb2ef45c9 in openjpa's branch
refs/heads/master from Mark Struberg
[ https://gitbox.apache.org/repos/asf?p=openjpa.git;h=61b3077 ]
OPENJPA-2842 log4j vs log4j2 logging fixed
* introduce new 'log4j2' LogFactory
* switch back old 'log4j' LogFactory to log4j-1.x
> openjpa.Log=log4j should automatically switch between log4j-1.x and 2.x
> -----------------------------------------------------------------------
>
> Key: OPENJPA-2842
> URL: https://issues.apache.org/jira/browse/OPENJPA-2842
> Project: OpenJPA
> Issue Type: Bug
> Components: logging
> Affects Versions: 3.1.2
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Major
> Fix For: 3.1.3
>
>
> Somewhen in 2018 we added support for log4j2. Sadly we killed log4j-1.x
> support (which is still widely in use).
>
> We should automatically detect which version of log4j is available and then
> use that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
