logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Norberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-978) log4j2 2.2 made breaking changes to public classes
Date Thu, 19 Mar 2015 08:18:38 GMT

    [ 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message