You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "PJ Fanning (Jira)" <ji...@apache.org> on 2022/05/29 08:53:00 UTC

[jira] [Commented] (LOG4J2-3524) support scala 3.0

    [ https://issues.apache.org/jira/browse/LOG4J2-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17543595#comment-17543595 ] 

PJ Fanning commented on LOG4J2-3524:
------------------------------------

[~mattsicker] would it be ok if I do a PR for this revert?

> 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
>
> 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.7#820007)