logback / LOGBACK-1704 [Open] Unchecked definition in LogbackMDCAdapter breaking custom adapters ============================== 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-1704 ============================== Issue created ------------------------------ Alessandro Zoffoli created this issue on 07/Nov/22 3:35 PM Summary: Unchecked definition in LogbackMDCAdapter breaking custom adapters Issue Type: Bug Affects Versions: 1.4.2, 1.4.3, 1.4.4 Assignee: Logback dev list Components: logback-classic Created: 07/Nov/22 3:35 PM Priority: Major Reporter: Alessandro Zoffoli Description: Hi,  Starting with 1.4.2 I spotted an issue when defining a custom `LogbackMDCAdapter`. In short, this change [https://github.com/qos-ch/logback/commit/7e3e2ae770c19724b0714c7f48fd33bbc67...] changed the definition of the `setContextMap` to be unchecked (`Map` vs. `Map<String, String>`). This is breaking custom adapters in Scala. I setup a minimal repro here: [https://github.com/AL333Z/logback-issue/blob/main/src/main/scala/MyLogbackAd...]   Restoring the definition to be `public void setContextMap(Map<String, String> contextMap)` should restore the functionality. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)