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 BE48310BD9 for ; Thu, 19 Mar 2015 08:18:38 +0000 (UTC) Received: (qmail 590 invoked by uid 500); 19 Mar 2015 08:18:38 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 536 invoked by uid 500); 19 Mar 2015 08: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 527 invoked by uid 99); 19 Mar 2015 08: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, 19 Mar 2015 08:18:38 +0000 Date: Thu, 19 Mar 2015 08:18:38 +0000 (UTC) From: "Daniel Norberg (JIRA)" To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (LOG4J2-978) log4j2 2.2 made breaking changes to public classes 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-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368685#comment-14368685 ] Daniel Norberg commented on LOG4J2-978: --------------------------------------- Yeah, maybe we should look into using the RFC 5424 layout instead of perpetuating the RFC 3164 millisecond precision hack. > log4j2 2.2 made breaking changes to public classes > -------------------------------------------------- > > Key: LOG4J2-978 > URL: https://issues.apache.org/jira/browse/LOG4J2-978 > Project: Log4j 2 > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Daniel Norberg > > The log4j2 2.2 release contained breaking changes to public classes, breaking direct uses and extenders of log4j2 interfaces. > E.g. https://github.com/apache/logging-log4j2/commit/3cdbbeddf19137d20fa6527d6620e88afcecb7f9 > Here is an example of the impact of this breaking change: https://github.com/spotify/logging-java/commit/3d2ca1c31a8ca3eabe1db378e2df48e0757e80e7 > Does log4j2 aim to follow semantic versioning? I am currently looking into the feasibility of taking log4j2 into use instead of logback, but this will not be possible if log4j2 will be having further breaking changes in minor releases. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org