Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 13CE61132F for ; Thu, 24 Jul 2014 03:18:39 +0000 (UTC) Received: (qmail 13353 invoked by uid 500); 24 Jul 2014 03:18:38 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 13119 invoked by uid 500); 24 Jul 2014 03:18:38 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 13107 invoked by uid 99); 24 Jul 2014 03:18:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 03:18:38 +0000 Date: Thu, 24 Jul 2014 03:18:38 +0000 (UTC) From: "Matt Sicker (JIRA)" To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (LOG4J2-735) logg4j-bom conflicting with spring-frameworkobom MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org