[ https://issues.apache.org/jira/browse/LOG4J2-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17576867#comment-17576867 ]
Florian Schmaus commented on LOG4J2-3524: ----------------------------------------- https://logging.apache.org/log4j/2.x/manual/scala-api.html mentions that "Scala 3 support has been recently added" and I find traces of Scala 3 in the repository (e.g., https://github.com/apache/logging-log4j-scala/blob/8ac6e7e391207db03da371d34584f186a403dea4/project/Dependencies.scala#L24). However the latest release on Maven Central is 12.0 and it appears that Scala 3 support is included in 12.1 onwards. Is there a chance to get a Scala 3 release of log4j-api-scala on Maven Central? > support scala 3.0 > ----------------- > > Key: LOG4J2-3524 > URL: https://issues.apache.org/jira/browse/LOG4J2-3524 > Project: Log4j 2 > Issue Type: Improvement > Components: Scala API > Affects Versions: Scala 12.1 > Reporter: PJ Fanning > Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > > This commit - > [https://github.com/apache/logging-log4j-scala/commit/63584bb16ec735fb162abf22db977b2832418e62] > - will mean that log4j-scala will only support Scala 3.1.x and not Scala > 3.0.x. > See [https://www.scala-lang.org/blog/2022/02/01/scala-3.1.1-released.html] > ``` > Scala 3 has excellent backward compatibility guarantees between the minor > versions. Right now, that means that code compiled with Scala 3.1 can depend > on libraries published with 3.0 without any problems. The opposite, hovewer, > is not true. Code compiled with 3.0 is not able to read dependencies compiled > with 3.1. After the recent release of Scala 3.1.0, we can see that libraries > should be really cautious with updating the compiler version, as it forces a > bump on every user of that library. > ``` > -- This message was sent by Atlassian Jira (v8.20.10#820010)