[
https://issues.apache.org/jira/browse/LOG4J2-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239451#comment-17239451
]
Ralph Goers commented on LOG4J2-2964:
-------------------------------------
I would start by taking a look at this PR. But yes, if plugins have to be
located via package scanning we should probably log a warn message that says 1)
use of the packages attribute is deprecated and will be removed in 3.0 and 2)
use of the packages attribute in 2.x should never be necessary if plugins have
been packaged correctly.
> Merge "packages" from several Configurations in Composite Configuration
> -----------------------------------------------------------------------
>
> Key: LOG4J2-2964
> URL: https://issues.apache.org/jira/browse/LOG4J2-2964
> Project: Log4j 2
> Issue Type: Improvement
> Components: Configuration, Core
> Reporter: Valery Yatsynovich
> Priority: Major
>
> When multiple configuration files are used and default merge strategy is in
> place, the attribute {{"packages"}} of the latest configuration takes
> precedence. However multiple configuration files may declare custom Appenders
> defined as {{@Plugin}} and these plugins may be declared in different
> packages.
> The proposed improvement is to perform merging of {{"packages"}} attributes
> from multiple configuration files in {{DefaultMergeStrategy}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
