logback / LOGBACK-1693 [Open] module-info declares jakarta.mail as a transitive dependency, but pom.xml does not ============================== 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-1693 ============================== Issue created ------------------------------ Sebastian Stenzel created this issue on 07/Oct/22 12:40 PM Summary: module-info declares jakarta.mail as a transitive dependency, but pom.xml does not Issue Type: Bug Affects Versions: 1.4.2, 1.4.3 Assignee: Logback dev list Attachments: Screenshot 2022-10-07 at 12.27.59.png Components: logback-core Created: 07/Oct/22 12:40 PM Environment: Maven 3.8.6 JDK 17 modular downstream project, which {{requires ch.qos.logback.core}}. Priority: Major Reporter: Sebastian Stenzel Description: Hooray, yet another modules-related issue 😉 After updating {{logback-core}} from 1.4.1 to 1.4.2+, I started getting this error from {{maven-compiler-plugin}}: {code:java} module not found: jakarta.mail {code} This surprised me, as I didn't declare any\{{requires}} in my module-info. However, when opening the module-info of logback-core, my IDE highlighted the problem: !Screenshot 2022-10-07 at 12.27.59.png! Note that missing modules don't cause any problems with {{requires static}}, as expected. However as soon as we add {{transitive}}, they are required by downstream modules. It is my understanding that {{transitive}} should only be used, if the module exposes public API which uses classes from the corresponding module. Is this really the case for {{jakarta.mail}}? If so, I guess they should be added as a (non-optional) dependency. ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)