[
https://issues.apache.org/jira/browse/LOG4J2-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315073#comment-17315073
]
ASF subversion and git services commented on LOG4J2-3004:
---------------------------------------------------------
Commit ede7b7aaeb92341cb69c910ea1fec11d9ce3a03f in logging-log4j2's branch
refs/heads/release-2.x from Volkan Yazici
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=ede7b7a ]
LOG4J2-3004 Revert TypeConverterRegistryTest breaking LoggersPluginTest and
ValidatingPluginWithFailoverTest.
> Migrate JsonTemplateLayout static resolvers to plugins
> ------------------------------------------------------
>
> Key: LOG4J2-3004
> URL: https://issues.apache.org/jira/browse/LOG4J2-3004
> Project: Log4j 2
> Issue Type: Improvement
> Components: JsonTemplateLayout
> Reporter: Volkan Yazici
> Assignee: Volkan Yazici
> Priority: Minor
> Fix For: 3.0.0, 2.15.0
>
>
> JsonTemplateLayout uses a static list of resolvers. While this makes it
> impossible ^1^ to update the set of resolvers used for the layout, e.g.,
> adding new user-provided custom resolvers, it is also old fashioned. Log4j
> has a great plugin system and it is leveraged by PatternLayout exactly for
> the same thing. This story aims to bring this improvement to
> JsonTemplateLayout too.
> ^1^ We can still allow the injection of a custom resolver factory in the
> layout configuration, but again, there is a better way to do it: plugins!
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
