[
https://issues.apache.org/jira/browse/LOG4J2-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15645389#comment-15645389
]
Ralph Goers commented on LOG4J2-1651:
-------------------------------------
Parsing ARBITRARY JSON is a minefield. We would not have arbitrary JSON, but a
very strict format. In essence, we would be parsing an array of a single type
of object. Each of the values can be defined as strings. That would be trivial
to parse, whether it is JSON or XML.
If you have a document that doesn't have a predefined format then parsing it
can be hard whether it is JSON, XML, an INI file, a property file or whatever.
Don't overthink the problem.
> Makes the dat format more user friendly
> ---------------------------------------
>
> Key: LOG4J2-1651
> URL: https://issues.apache.org/jira/browse/LOG4J2-1651
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Romain Manni-Bucau
> Attachments: Log4j2Plugins.xml
>
>
> The dat format used by the plugin is not that friendly when users want to
> shade log4j2 and manual manipulation is hard and require some advanced shade
> ability (concretely you need to write your own PluginCache serialization if
> you select a subpart of log4j2 to go in your shade)
> Would be great to provide an easier and smoother way to do that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
