[ https://issues.apache.org/jira/browse/LOG4J2-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16990328#comment-16990328 ]
ASF subversion and git services commented on LOG4J2-2674: --------------------------------------------------------- Commit d093ae164b8e5a453b6e5d5f57cd18dbb22c7f53 in logging-log4j2's branch refs/heads/master from Ralph Goers [ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=d093ae1 ] LOG4J2-2674 - Change the name of the ConfigurationSource > CompositeConfiguration misleading configuration source > ------------------------------------------------------ > > Key: LOG4J2-2674 > URL: https://issues.apache.org/jira/browse/LOG4J2-2674 > Project: Log4j 2 > Issue Type: Improvement > Components: Core > Affects Versions: 2.8.1 > Reporter: Anton Korenkov > Priority: Trivial > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Sometimes we are using CompositeConfiguration in our code. During last > investigation we've found out that configuration source passed during > constructor call is 'NULL_SOURCE'. It's a bit confusing because it conflicts > with NULL_SOURCE definition > {noformat} > /** > * ConfigurationSource to use with Configurations that do not require a > "real" configuration source. > */ > public static final ConfigurationSource NULL_SOURCE = new > ConfigurationSource(new byte[0]); > {noformat} > because actually we have a 'composite' or 'multiple' configuration sources > which will be used later to produce real configuration. > The question is: do you mind to create 'COMPOSITE_SOURCE' constant and use it > in CompositeConfiguration? -- This message was sent by Atlassian Jira (v8.3.4#803005)