SLF4J / SLF4J-602 [Open] JCL-Over-SLF4J Module Definition does not specify the service loader (Issue #414)
============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/SLF4J-602 ============================== Issue created ------------------------------ Ceki Gülcü created this issue on 14/Apr/24 9:54 Summary: JCL-Over-SLF4J Module Definition does not specify the service loader (Issue #414) Issue Type: Bug Assignee: SLF4J developers list Created: 14/Apr/24 9:54 Priority: Major Reporter: Ceki Gülcü External issue URL: https://github.com/qos-ch/slf4j/issues/414 Description: Guys, The module definition for the jcl-over-slf4j unfortunately does not specify the service loader for org.apache.commons.logging.LogFactory When executing applications in a built JRE (Using JLink or JPackage), the services are loaded from their module definitions, and the functionality is not loaded. Could you please possible update the module definition - `module org.apache.commons.logging { requires org.slf4j; exports org.apache.commons.logging; provides org.apache.commons.logging.LogFactory with org.apache.commons.logging.impl.SLF4JLogFactory; } ` Much appreciated ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af) _______________________________________________ slf4j-dev mailing list slf4j-dev@qos.ch https://mailman.qos.ch/cgi-bin/mailman/listinfo/slf4j-dev
