| Summary: | Add Import-Package ch.qos.logback.access.jetty.v7 to bundle org.eclipse.jetty.osgi.boot.logback | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Christian Brensing <christian.brensing> |
| Component: | osgi | Assignee: | Hugues Malphettes <hmalphettes> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | jetty-inbox |
| Version: | unspecified | ||
| Target Milestone: | 7.1.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Thanks Christian for reporting this. I have committed the suggested change for jetty-7.2 and jetty-7.1 Resolved -> Closed |
Build Identifier: The fragment bundle org.eclipse.jetty.osgi.boot.logback injects the logback dependencies into the Boot-Bundle. That works fine with LOGBack-Classic. In order to use LOGBack-Access as an alternative to the Jetty-Builtin-Request-Logger, the package ch.qos.logback.access.jetty.v7 must be (optionally) injected as well, otherwise a CNFE will be thrown. jetty.xml example: <Ref id="RequestLog"> <Set name="requestLog"> <New id="RequestLogImpl" class="ch.qos.logback.access.jetty.v7.RequestLogImpl"/> </Set> </Ref> It would be nice, if the package ch.qos.logback.access.jetty.v7 could be added as an optional import to the Import-Package list: Import-Package: ..., ch.qos.logback.access.jetty.v7;resolution:=optional Reproducible: Always