[
https://issues.apache.org/jira/browse/LOG4J2-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239511#comment-17239511
]
Remko Popma commented on LOG4J2-2964:
-------------------------------------
{quote}use of the packages attribute is deprecated and will be removed in 3.0
{quote}
Interesting, I was not aware of this. I remember having an issue once that I
was able to resolve by using the packages attribute instead of relying on the
annotation processor. This was a long time ago, I don't remember the details. I
would not mind keeping the packages attribute as a fallback mechanism (and to
me it is okay if the fallback mechanism is not fast).
Agreed that the primary mechanism should be the annotation processor, and the
perf improvement with ServiceLoader is nice.
> 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)
