[
https://issues.apache.org/jira/browse/LOG4J2-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558152#comment-17558152
]
Pavel_K commented on LOG4J2-3451:
---------------------------------
[~pkarwasz] Thank you very much for such detailed explanation. Then I think
this issue should be closed, because JPMS services are much better then package
scanning and particularly if we work in JPMS. So, if module path, then
everything that is on module path is JPMS module. What do you think?
> Custom appenders on module path must be found
> ---------------------------------------------
>
> Key: LOG4J2-3451
> URL: https://issues.apache.org/jira/browse/LOG4J2-3451
> Project: Log4j 2
> Issue Type: Improvement
> Affects Versions: 2.14.1
> Reporter: Pavel_K
> Assignee: Piotr Karwasz
> Priority: Major
>
> Currently if custom appender is added via config, something like this:
> {code:java}
> <Configuration packages="com.yourcompany.yourcustomappenderpackage">
> <Appenders>
> <MyCustomAppender name="ABC" otherAttribute="...">
> ...
> </Appenders>
> <Loggers><Root><AppenderRef ref="ABC" /></Root></Loggers>
> </Configuration>
> {code}
> Log4j2 will find this appender class only if this class is on class path. I
> suggest that appenders on module path must also be found.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
