Re: drop scala....version from artifact ;)

Flink, Gearpump, Spark, and GCE provisioning are affected by this "issue". Dropping it if we never manage 2 versions is nicer for end users IMHO but I'm fine keeping it. Just would like to ensure it is uniform accross the whole projet. Romain Manni-Bucau @rmannibucau

Re: drop scala....version from artifact ;)

I think Kafka IO doesn't have a transitive Scala dependency anymore because Kafka removed that from their client code a while ago. Best, Aljoscha > On 1. Feb 2018, at 14:48, Jean-Baptiste Onofré wrote: > > I got your point Aljoscha. Flink runner is the only module using this suffix. > > Spark

Re: drop scala....version from artifact ;)

I got your point Aljoscha. Flink runner is the only module using this suffix. Spark runner, Kafka IO, and others also have a scala dep but don't use the suffix. So, we have three options: 1. We leave as it is right now 2. We remove suffix from Flink runner 3. We add suffix to other modules (Spar

Re: drop scala....version from artifact ;)

I think it's not wise to remove the Scala suffix. When using the Flink Runner you have to make sure that the Scala version matches the Scala version of the Flink Cluster. And I think comparing the suffix of your flink-runner dependency and the suffix of your Flink dist is an easy way of doing th

Re: drop scala....version from artifact ;)

Hi Romain, AFAIR only Flink runner uses scala version in the artifactId. +1 for me. Regards JB On 01/31/2018 04:45 PM, Romain Manni-Bucau wrote: > Hi guys > > since beam supports a single version of runners why not dropping the scala > version from the artifactId? > > ATM upgrades are painful

drop scala....version from artifact ;)

Hi guys since beam supports a single version of runners why not dropping the scala version from the artifactId? ATM upgrades are painful cause you upgrade beam version+ runner artifactIds. wdyt? Romain Manni-Bucau @rmannibucau | Blog