[
https://issues.apache.org/jira/browse/LOG4J2-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519092#comment-17519092
]
Piotr Karwasz commented on LOG4J2-3463:
---------------------------------------
Hello [~smarkhedkar],
my PR has a rather high risk-to-reward ratio, so I will not rush to merge it
until I check many usage cases.
You can however compile the library yourself. This requires:
# installing a Java 8 and Java 9+ (e.g. Java 11) JDK on your system,
# setting {{JAVA_HOME}} to the path of the Java 8 JDK.
# cloning the branch of the PR:
{noformat}
git clone https://github.com/ppkarwasz/logging-log4j2.git
{noformat}
# installing the appropriate {{toolchains.xml}} file in the {{.m2}} folder of
your home directory and adapting the paths to the ones used by your system,
# running the Maven wrapper in the project's directory:
{noformat}
./mvnw -DskipTests=true clean install
{noformat}
The freshly compiled jars will be in your local Maven repository ({{.m2}}
directory in your home directory).
> java.util.ServiceConfigurationError: org.apache.logging.log4j.spi.Provider:
> Provider org.apache.logging.log4j.core.impl.Log4jProvider not a subtype
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3463
> URL: https://issues.apache.org/jira/browse/LOG4J2-3463
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Core, Log4j 1.2 bridge, Web/Servlet
> Affects Versions: 2.17.3
> Environment: Configuration:
> Using bridge api 2.17.3 latest snapshot. Also using log4j-web, log4j-api,
> log4j-core (all 2.17.3 snapshot). A wrapper class is used for configuration
> across applications running on tomcat.
> Reporter: Swapnil Markhedkar
> Priority: Blocker
> Attachments: Provider error.txt
>
>
> Came across this error while using tomcat at application level. Similar to
> https://issues.apache.org/jira/browse/LOG4J2-2055, but error persists even
> when added 2.10 jars.
> In depth stack trace has been attached as text file.
> NOTE: Tomcat server and it's logging is working fine.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
