[
https://issues.apache.org/jira/browse/KAFKA-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709915#comment-13709915
]
Scott Carey commented on KAFKA-717:
-----------------------------------
{quote}that would be easiest for us would be post-0.8 (i.e. 0.8.1/trunk){quote}
(Can the wiki-text plugin be enabled for this project?)
That's fine, I'm happy maintaining our own fork to handle 2.10.x for now.
This is about how to move forward long term, which requires trimming support
for old versions. 2.11 (a 'performance' release) will be out in 6 months or
so, and 2.8.x will become even more difficult to support in conjunction.
In this case, the big pain point is the Java conversions/converters code in the
Java API. New client APIs in Kafka can simultaneously make the code more
portable across Scala versions, since incompatibilities are generally due to
library changes and not language changes.
> scala 2.10 build support
> ------------------------
>
> Key: KAFKA-717
> URL: https://issues.apache.org/jira/browse/KAFKA-717
> Project: Kafka
> Issue Type: Improvement
> Components: packaging
> Affects Versions: 0.8
> Reporter: Viktor Taranenko
> Labels: build
> Attachments: 0001-common-changes-for-2.10.patch,
> 0001-common-changes-for-2.10.patch,
> 0001-KAFKA-717-Convert-to-scala-2.10.patch,
> 0002-java-conversions-changes.patch, 0002-java-conversions-changes.patch,
> 0003-add-2.9.3.patch, 0003-add-2.9.3.patch,
> 0004-Fix-cross-compile-of-tests-update-to-2.10.2-and-set-.patch,
> KAFKA-717-complex.patch, KAFKA-717-simple.patch, kafka_scala_2.10.tar.gz
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
