[logback-dev] [JIRA] Updates for LOGBACK-1676: logback-access cannot be used with Jetty 9.4.48.v20220622

[QOS.CH (JIRA)]

logback / LOGBACK-1676 [Open]
logback-access cannot be used with Jetty 9.4.48.v20220622

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

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/LOGBACK-1676

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

Dr. Domagoj Ćosić created this issue on 13/Sep/22 9:27 PM
Summary:              logback-access cannot be used with Jetty 9.4.48.v20220622
Issue Type:           Bug
Affects Versions:     1.3.0
Assignee:             Logback dev list
Components:           logback-access
Created:              13/Sep/22 9:27 PM
Priority:             Major
Reporter:             Dr. Domagoj Ćosić
Description:
  There two flaws preventing usage wir that version, despite of dependencies page in the documentation declaring the compatibility:
   # logback-access declares dependency on Servlet API 4.0.0 (manifest) or 4.0.1 (documentation). Jetty 9.4.48 provides only a Servlet API 3.1 compliant implementation (see https://www.eclipse.org/jetty/). Is 4.x a real requirement?
   # logback-access specifies version=“9.4.48.v20220622” for all Jetty packages in Import-Package. Jetty 9.4.48.v20220622 declares *bundle-version*=“9.4.48.v20220622” for all packages in Export-Package but *version*=“9.4.48”. Version “9.4.48” < “9.4.48.v20220622” when it comes to comparing, so the requirement cannot be matched. Jetty packages cannot be wired. Loading Jetty classes by logback-access thus fails (but not the resolution prior to it, dependencies are optional).


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