[
https://issues.apache.org/jira/browse/LOG4J2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562673#comment-17562673
]
Alexander Picoli commented on LOG4J2-3547:
------------------------------------------
The workaround I'm using and at least for 2.17.2 works, is to keep using the
log4j-1.2-2.17.1.jar . But it is like having a loose hot wire on the ground,
and have people stepping over it all the time.
> Incompatible behavior for log4j 1.2 bridge regarding PropertiesConfiguration
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-3547
> URL: https://issues.apache.org/jira/browse/LOG4J2-3547
> Project: Log4j 2
> Issue Type: Bug
> Components: Log4j 1.2 bridge
> Affects Versions: 2.18.0, 2.17.2
> Reporter: Alexander Picoli
> Priority: Major
>
> Log4j2 1.2 bridge api has been since forever a no-op regarding the
> PropertiesConfiguration.
> This feature is actively used in our projects: we depend on third party apis
> that tries to override log4j configuration by calling
> PropertyConfiguration.configure with custom property files.
> We use the advanced features from log4j2 with those legacy code to, among
> other things, cope with GDPR (we specify a log4j2 custom made RedactorLayout
> ) to be used with this legacy code, and count with the fact that the
> log4j2.xml file configuration is not overriden elsewhere.
> I do reckon that this change makes log4j 1.2 to 2.0 transition easier for
> most people, but this should be something that could be turned off somehow.
> *Possible solutions:*
> * add a log4j-1.2-noconfig jar that doesn't implement the
> PropertiesConfiguration.
> * add a property or environment variable that allows to enable/disable this
> feature.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
