Hi Gili,
SLF4J API will not change between 1.8.0-beta2 and 1.8.0. You can safely rely on 1.8.0-beta2 if JPMS is a requirement.
If you can wait a bit, wait for 1.7.26 addressing SLF4J-420. HTH, [1] https://jira.qos.ch/browse/SLF4J-420 -- Ceki Gülcü On 29.11.2018 16:50, cowwoc2020 wrote:
Hi, I'd like to publish my library to Maven Central but it depends upon slf4j and we're advised not to publish artifacts to central if they depend upon modules with Automatic Filename-based Naming. The latest stable version of slf4j-api is 1.7.25 but it relies upon Automatic Filename-based Naming. Version 1.8.0-beta2 is supposed to be compatible with JPMS but it isn't a stable release. What is the advised behavior in this situation? Thank you, Gili
_______________________________________________ slf4j-user mailing list slf4j-user@qos.ch http://mailman.qos.ch/mailman/listinfo/slf4j-user
