[
https://issues.apache.org/jira/browse/LOG4J2-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072744#comment-14072744
]
Matt Sicker commented on LOG4J2-735:
------------------------------------
I think I have a fix for this actually.
> logg4j-bom conflicting with spring-frameworkobom
> ------------------------------------------------
>
> Key: LOG4J2-735
> URL: https://issues.apache.org/jira/browse/LOG4J2-735
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.0
> Reporter: Poorna Subhash P
>
> I have spring-framework-bom included in my pom.xml for long time. Today, when
> I included log4j-bom into my pom.xml, the whole system broke. On my analysis,
> I have found that log4j parent pom has included all spring dependencies with
> 3.2.8 version.
> Hence the pom has imported two version of spring dependendencies 4.0.4 and
> 3.2.8 and all unwanted dependency conflicts.
> following is debug output on maven build.
> [DEBUG] org.springframework:spring-test:jar:4.0.4.RELEASE:test
> [DEBUG] org.springframework:spring-core:jar:3.2.8.RELEASE:test (version
> managed from 4.0.4.RELEASE by org.apache.logging.log4j:log4j:2.0)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
