[
https://issues.apache.org/jira/browse/KAFKA-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992994#comment-15992994
]
ASF GitHub Bot commented on KAFKA-4422:
---------------------------------------
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/2956
KAFKA-4422: Drop support for Scala 2.10
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijuma/kafka kafka-4422-drop-support-scala-2.10
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2956.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2956
----
----
> Drop support for Scala 2.10
> ---------------------------
>
> Key: KAFKA-4422
> URL: https://issues.apache.org/jira/browse/KAFKA-4422
> Project: Kafka
> Issue Type: Task
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Labels: kip
> Fix For: 0.11.0.0
>
>
> Now that Scala 2.12 has been released, we should drop support for Scala 2.10
> in the next major Kafka version so that we keep the number of supported
> versions at 2. Since we have to compile and run the tests on each supported
> version, there is a non-trivial cost from a development and testing
> perspective.
> The clients library is in Java and we recommend people use the Java clients
> instead of the Scala ones, so dropping support for Scala 2.10 should have a
> smaller impact than it would have had in the past. Scala 2.10 was released in
> January 2013 and support ended in March 2015.
> Once we drop support for Scala 2.10, we can take advantage of APIs and
> compiler improvements introduced in Scala 2.11 (introduced in April 2014):
> http://scala-lang.org/news/2.11.0
> Link to KIP:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-119%3A+Drop+Support+for+Scala+2.10+in+Kafka+0.11
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
