(I found this stuck in my outbox, sorry for the delayed response)
Hi,
Thank you, I finally was able to configure maven to exclude that logging
implementation. But now I'm having an issue building a Spring-Boot executable
WAR with embedded Tomcat, for some reason, when I "spring-boot:run" it,
(sorry for bad formatting Outlook-for-Mac doesn't support Internet quoting)
Thanks Mark, I did that until I finally was able to exclude it altogether.
-Chris
On 1/17/20, 10:20 AM, "Mark H. Wood" wrote:
For the version problem, I would try adding something like:
On Thu, Jan 16, 2020 at 03:13:17PM +, 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
Ultimately if you deduce the problem, file a JIRA issue and share it with
me; I will look into it. I care about this matter too; I hate having to
exclude logging dependencies on the consuming end.
~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley
On
--- 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
On Thu, Jan 16, 2020 at 02:03:06AM +, Wolf, Chris (ELS-CON) wrote:
[snip]
> There are several issues:
>
> 1. I don’t want log4j-slf4j-impl at all
> 2. Somehow the version of “log4j-slf4j-impl” being used for the build is
> 2.7 rather then the expected 2.11.0
> 3. Due to the version
