On Thu, Jan 16, 2020 at 03:13:17PM +0000, Wolf, Chris (ELS-CON) wrote: > --- original message --- > It looks to me as though solr-core is not the only artifact with that > dependency. The first thing I would do is examine the output of 'mvn > dependency:tree' to see what has dragged log4j-slf4j-impl in even when > it is excluded from solr-core. > --- end of original message --- > > Hi, that's the first thing I did and *only* solr-core is pulling in > log4j-slf4j-impl, but there is more weirdness to this. When I build as a WAR > project, then version 2.11.0 of in log4j-slf4j-impl is pulled in which > results in "multiple implementations" warning and is non-fatal. > > However, when building as a spring-boot executable jar, for some reason, it > pulls in version 2.7 rather then 2.11.0 resulting in fatal > "ClassNotFoundException: org.apache.logging.log4j.util.ReflectionUtil"
For the version problem, I would try adding something like:
<dependencyManagement>
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-slf4j-impl</artifactId>
<version>2.11.0</version>
</dependency>
</dependencyManagement>
to pin down the version no matter what is pulling it in. Not ideal,
since you want to be rid of this dependency altogether, but at least
it may allow the spring-boot artifact to run, until the other problem
is sorted.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu
signature.asc
Description: PGP signature
