[slf4j-dev] [JIRA] Updates for SLF4J-577: Export slf4j packages in version 1 and 2 in OSGi-Manifests

QOS.CH (JIRA) noreply-jira at qos.ch
Tue Mar 14 11:15:00 CET 2023


SLF4J / SLF4J-577 [Open]
Export slf4j packages in version 1 and 2 in OSGi-Manifests

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

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

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

Ceki Gülcü created this issue on 14/Mar/23 11:06 AM

Summary:              Export slf4j packages in version 1 and 2 in OSGi-Manifests
Issue Type:           Bug
Assignee:             SLF4J developers list
Created:              14/Mar/23 11:05 AM
Environment:
  
  
  
Priority:             Major
Reporter:             Ceki Gülcü
Description:
  Hannes Wellmann on 16/Dec/22 3:24 PM
  Issue https://jira.qos.ch/browse/SLF4J-577 turned out to be a false alarm.
  
  However this made me think about this issue a bit more and actually only the packages that are relevant for clients should be exported in a version 1.x.
  
  The package-info for {{org.slf4j.spi}} states that this package should not be used by clients.
  @ceki can you clarify if anything from {{org.slf4j.helpers}} respectivly {{org.slf4j.event}} were relevant for clients in{{ SLF4J-1?}} If there is nothing it should not be necessary they should not be exported in version 1 as well.
  
  This would also solve the problem that a SLF4J-1 binding would have been wired to the slf4j-api in version 2, but if they e.g. import {{org.slf4j.spi}} in version 1 it can only be wired to slf4j-api in version 1.
  


==============================
 This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)



More information about the slf4j-dev mailing list