[
https://issues.apache.org/jira/browse/LOG4J2-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286546#comment-17286546
]
Ralph Goers commented on LOG4J2-3003:
-------------------------------------
Somehow my comment from the mailing list discussion got overlooked.
{code:java}
Volkan, I am fine with deleting those modules however that would require that
you make sure that you replace the existing Layouts with ones that use
JsonTemplateLayout templates, take the same configuration parameters and
produce the same results.
In other words, when people move from 2.x to 3.x we want to minimize the
changes they have to make to their applications. All existing configurations
should continue to work. Custom Plugins should require recompilation but
nothing more. Hopefully that would cover 95% of our users.
{code}
> Delete log4j-layout-jackson* modules
> ------------------------------------
>
> Key: LOG4J2-3003
> URL: https://issues.apache.org/jira/browse/LOG4J2-3003
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Volkan Yazici
> Assignee: Volkan Yazici
> Priority: Minor
> Fix For: 2.15.0, 3.0.0.
>
>
> [As discussed in the dev mailing
> list|https://lists.apache.org/thread.html/rbcca0c027889c95ba0493a362fd8c7e280aba2d7e258060660bb6f3d%40%3Cdev.logging.apache.org%3E],
> this story aims to delete the deprecated {{log4j\-layout\-jackson*}} modules
> from the *master* branch:
> * log4j-layout-jackson
> * log4j-layout-jackson-json
> * log4j-layout-jackson-xml
> * log4j-layout-jackson-yaml
> Note that these first need to be mark as deprecated in the *release-2.x*
> branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
