SLF4J / SLF4J-495 [Open] Binary compatibility between release and alpha version ============================== Here's what changed in this issue in the last few minutes. There is 1 comment. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-495 ============================== 1 comment ------------------------------ Alexander Krimm on 16/Jul/20 11:35 PM Thank you for your quick response which matches the behavior we observed. This [manual section on binary compatibiliy|http://example.com] led me to believe that such a configuration should work: bq. However, from the client's perspective all versions of slf4j-api are compatible. *Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M.* You only need to ensure that the version of your binding matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used by a given dependency in your project. You can always use any version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its binding match, you should be fine. This is also repeated in the [FAQ|http://slf4j.org/faq.html#compatibility]: bq. From the clients perspective, the SLF4J API is backward compatible for all versions. This means than you can upgrade from SLF4J version 1.0 to any later version without problems. *Code compiled with slf4j-api-versionN.jar will work with slf4j-api-versionM.jar for any versionN and any versionM*. To date, binary compatibility in slf4j-api has never been broken. For application development this is not a big deal but as a library developer, using the alpha API seems to force all of your users to also use the alpha API and corresponding bindings, which may or may not be acceptable for them, while the manual/faq suggest that there is little impact in upgrading. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)