[
https://issues.apache.org/jira/browse/LOG4J2-1308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182326#comment-15182326
]
Remko Popma edited comment on LOG4J2-1308 at 3/6/16 9:06 PM:
-------------------------------------------------------------
Can you update the description with what the configuration would look like
after the change you propose? Also, when I first read it I thought that
"backwards compatibility" referred to the 1.2 properties format, but now I
think you mean the format we introduced in 2.4. It is the latter, right?
was (Author: [email protected]):
Can you update the description with how the configuration would look like after
the change you propose? Also, when I first read it I thought that "backwards
compatibility" referred to the 1.2 properties format, but now I think you mean
the format we introduced in 2.4. It is 2.4 right?
> Remove need to pre-specify appender names et al. in property file config
> format
> -------------------------------------------------------------------------------
>
> Key: LOG4J2-1308
> URL: https://issues.apache.org/jira/browse/LOG4J2-1308
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configurators
> Affects Versions: 2.4, 2.5
> Reporter: Matt Sicker
> Assignee: Matt Sicker
>
> In the .properties config file format, several plugin types currently require
> you to declare names ahead of time. For instance:
> {code}
> appenders = foo, bar, baz
> appender.foo.type = Console
> appender.bar.type = File
> appender.baz.type = List
> # ...
> {code}
> These names should be inferable by their first usage. Then the appenders,
> filters, loggers, etc., properties can all be safely ignored for backwards
> compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
