You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "Matt Sicker (Jira)" <ji...@apache.org> on 2022/05/23 03:05:00 UTC

[jira] [Commented] (LOG4J2-3299) Add structured format for configuring PropertiesUtil settings

    [ https://issues.apache.org/jira/browse/LOG4J2-3299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540740#comment-17540740 ] 

Matt Sicker commented on LOG4J2-3299:
-------------------------------------

As part of preparation for this, I'm going to look at abstracting PropertiesUtil into an interface and make some updates to code that looks up PropertiesUtil manually to instead take it as an injected dependency.

> Add structured format for configuring PropertiesUtil settings
> -------------------------------------------------------------
>
>                 Key: LOG4J2-3299
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3299
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: API, Configuration
>            Reporter: Matt Sicker
>            Priority: Major
>
> The existing list of system properties and environment variables supported by Log4j is enormous. It would be great to improve PropertiesUtil to support a more structured format (like JSON or YAML) to better organize settings. This can enable shipping a default config along with allowing users to override settings in their own config file. This feature can be compared with Spring Boot's bootstrap settings (or even Spring's general application.yaml/application.properties parsing).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)