[
https://issues.apache.org/jira/browse/LOG4J2-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549215#comment-14549215
]
jeremy franklin-ross commented on LOG4J2-978:
---------------------------------------------
Hi [[email protected]] and [~garydgregory], I truly appreciate your work.
Please reconsider your stance on semantic versioning. On the one hand you've
invited developers to extend core functionality through plugins, on the other
you've taken away one of the key tools we use to maintain our code when doing
so (semantic versioning). The recent 2.3 release broke several plugins (and the
services that rely on them) in my company by virtue of charsets class
disappearing in 2.3.
I understand you want core and api to be versioned together and I understand
your reluctance to push forward major version when introducing non-backwards
compatible changes only to core. Might I suggest that instead of releasing
non-backwards compatible core 2.X changes that you simply use deprecation and
schedule all deprecated pathways for deletion in 3.x?
> 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: [email protected]
For additional commands, e-mail: [email protected]
