[slf4j-dev] [JIRA] Updates for SLF4J-574: slf4j OSGi metadata missing "uses" clauses

[QOS.CH (JIRA)]

SLF4J / SLF4J-574 [Open]
slf4j OSGi metadata missing "uses" clauses

==============================

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-574

==============================
 Issue created
------------------------------

Jonah Graham created this issue on 09/Dec/22 6:34 PM
Summary:              slf4j OSGi metadata missing "uses" clauses
Issue Type:           Bug
Assignee:             SLF4J developers list
Created:              09/Dec/22 6:34 PM
Environment:          Running SLF4J in OSGi environment
Priority:             Major
Reporter:             Jonah Graham
Description:
  When using SLF4J in an OSGi environment, the wiring can go wrong because SLF4J does not include uses clauses in the MANIFEST.MF.
  
  
  This leads to errors like:
  
   
   loader constraint violation: 
    when resolving method 'org.slf4j.ILoggerFactory org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()' 
    the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @3a07fd19 of the current class, 
      org/slf4j/LoggerFactory, and 
    the class loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @773560cf for the method's defining class, 
      org/slf4j/impl/StaticLoggerBinder, 
    have different Class objects for the type org/slf4j/ILoggerFactory used in the signature
    (org.slf4j.LoggerFactory is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @3a07fd19,
         parent loader 'platform'; 
     org.slf4j.impl.StaticLoggerBinder is in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @773560cf, 
         parent loader 'platform')
   
  
  {{}}
  
  {{}}


==============================
 This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)