You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Daniel Norberg (JIRA)" <ji...@apache.org> on 2015/03/19 06:23:38 UTC
[jira] [Created] (LOG4J2-978) log4j2 2.2 made breaking changes to
public classes
Daniel Norberg created LOG4J2-978:
-------------------------------------
Summary: 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