[jira] [Resolved] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

[ https://issues.apache.org/jira/browse/KAFKA-4421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-4421. Resolution: Fixed Assignee: Ewen Cheslack-Postava > Update release process so that Scala 2

[jira] [Commented] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

this automatically: https://github.com/apache/kafka/pull/2795/files So, we can close this once that script is merged. Once we move to Java 8, we can enable Scala 2.12 by default and simplify the release script. > Update release process so that Scala 2.12 artifacts are pu

[jira] [Commented] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

o be written down as well. > Update release process so that Scala 2.12 artifacts are published > - > > Key: KAFKA-4421 > URL: https://issues.apache.org/jira/browse/KAFKA-4421 >

[jira] [Comment Edited] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

8 PM: - [~guozhang], you didn't change JAVA_HOME to point to Java 8? was (Author: ijuma): @guozhangwang, you didn't change JAVA_HOME to point to Java 8? > Update release process so that Scala 2.12 artifa

[jira] [Commented] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

A_HOME to point to Java 8? > Update release process so that Scala 2.12 artifacts are published > - > > Key: KAFKA-4421 > URL: https://issues.apache.org/jira/browse/KAFKA-4421 >

[jira] [Commented] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

f we want to officially include 2.12 artifacts. > Update release process so that Scala 2.12 artifacts are published > - > > Key: KAFKA-4421 > URL: https://issues.apache.org/jir

[jira] [Commented] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

with Scala 2.12 artifacts, I was hoping he would update the release process page to include the additional steps. As you said, it's a bit odd to do it for 0.10.1.1, but not 0.10.2.0. If the process is not too onerous, I'd just publish Scala 2.12 artifacts for every future release. We

[jira] [Commented] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

for this earlier. How do we want to handle Scala 2.12 until we remove java 7 support? > Update release process so that Scala 2.12 artifacts are published > - > > Key: KAFKA-4421 > URL: https:

scala 2.12 artifacts

Hi all, With the recent release of scala 2.12 the community has been working toward getting libraries released as 2.12 compiled binaries. Although Kafka isn’t a typical development library the scalatest-embedded-kafka project (https://github.com/manub/scalatest-embedded-kafka

[jira] [Created] (KAFKA-4421) Update release process so that Scala 2.12 artifacts are published

Ismael Juma created KAFKA-4421: -- Summary: Update release process so that Scala 2.12 artifacts are published Key: KAFKA-4421 URL: https://issues.apache.org/jira/browse/KAFKA-4421 Project: Kafka