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

Josep Prat commented on KAFKA-12954:
------------------------------------

Hi [~ijuma] I did a draft PR with the changes that would be needed to support 
Scala 3.

You can evaluate it yourself here: [https://github.com/apache/kafka/pull/10934]

The changes are minimal and automatic (right import and a rename of a method). 
The branch in that PR can compile Kafka in both 2.13 and 3.0 versions.
{code:java}
./gradlew -PscalaVersion=3.0 compileScala
{code}
{code:java}
./gradlew -PscalaVersion=2.13 compileScala
{code}

> Add Support for Scala 3 in 4.0.0
> --------------------------------
>
>                 Key: KAFKA-12954
>                 URL: https://issues.apache.org/jira/browse/KAFKA-12954
>             Project: Kafka
>          Issue Type: Improvement
>          Components: build
>            Reporter: Josep Prat
>            Assignee: Josep Prat
>            Priority: Major
>              Labels: needs-kip
>             Fix For: 4.0.0
>
>
> This is a follow up task from 
> https://issues.apache.org/jira/browse/KAFKA-12895, in which Scala 2.12 
> support will be dropped.
> It would be good to, at the same time, add support for Scala 3.
> Initially it would be enough to only make the code compile with Scala 3 so we 
> can generate the proper Scala 3 artifacts, this might be achieved with the 
> proper compiler flags and an occasional rewrite.
> Follow up tasks could be created to migrate to a more idiomatic Scala 3 
> writing if desired.
> If I understand it correctly, this would need a KIP as we are modifying the 
> public interfaces (new artifacts). If this is the case, let me know  and I 
> will write it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to