[
https://issues.apache.org/jira/browse/LOG4J2-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Beh updated LOG4J2-3063:
------------------------------
Description:
log4j-api's module-info is missing "provides PropertySource ..." directives.
This causes the ServiceLoader to not be able to detect
SystemPropertiesPropertySource when running on the module path.
Reproducer here: [https://github.com/A248/Log4j2-3063] . The application is
intended to be configured with the log4j2-debug.xml configuration passed
through -Dlog4j2.configurationFile. However, log4j2.configurationFile is only
effective when running on the classpath. Running on the modulepath requires
using the legacy property log4j.configurationFile.
was:
log4j-api's module-info is missing "provides PropertySource ..." directives.
This causes the ServiceLoader to not be able to detect
SystemPropertiesPropertySource when running on the module path.
Reproducer here: [https://github.com/A248/Log4j2-3063] .
> Missing provides directives in module-info cause system properties to not
> accept post log4j 2.10 normalized versions
> --------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3063
> URL: https://issues.apache.org/jira/browse/LOG4J2-3063
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Anand Beh
> Priority: Major
>
> log4j-api's module-info is missing "provides PropertySource ..." directives.
> This causes the ServiceLoader to not be able to detect
> SystemPropertiesPropertySource when running on the module path.
> Reproducer here: [https://github.com/A248/Log4j2-3063] . The application is
> intended to be configured with the log4j2-debug.xml configuration passed
> through -Dlog4j2.configurationFile. However, log4j2.configurationFile is only
> effective when running on the classpath. Running on the modulepath requires
> using the legacy property log4j.configurationFile.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
