Return-Path: X-Original-To: apmail-flink-user-archive@minotaur.apache.org Delivered-To: apmail-flink-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 120AF18DC4 for ; Mon, 22 Feb 2016 18:02:05 +0000 (UTC) Received: (qmail 38818 invoked by uid 500); 22 Feb 2016 18:01:55 -0000 Delivered-To: apmail-flink-user-archive@flink.apache.org Received: (qmail 38721 invoked by uid 500); 22 Feb 2016 18:01:55 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@flink.apache.org Delivered-To: mailing list user@flink.apache.org Received: (qmail 38712 invoked by uid 99); 22 Feb 2016 18:01:55 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2016 18:01:55 +0000 Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id C960A1A023C for ; Mon, 22 Feb 2016 18:01:54 +0000 (UTC) Received: by mail-wm0-f46.google.com with SMTP id c200so184384378wme.0 for ; Mon, 22 Feb 2016 10:01:54 -0800 (PST) X-Gm-Message-State: AG10YORDSI48xn6AE2AZwSw/6+iIgk6RYCsU1E9h0u4yCW7gVI65jcfROARbFEXwF/79H3qv2035C9KUUMl9Uw== MIME-Version: 1.0 X-Received: by 10.28.224.87 with SMTP id x84mr14530896wmg.32.1456164113463; Mon, 22 Feb 2016 10:01:53 -0800 (PST) Received: by 10.28.113.129 with HTTP; Mon, 22 Feb 2016 10:01:53 -0800 (PST) In-Reply-To: <1456161628001-5078.post@n4.nabble.com> References: <1455313448712-4897.post@n4.nabble.com> <1455547299823-4924.post@n4.nabble.com> <1456161628001-5078.post@n4.nabble.com> Date: Mon, 22 Feb 2016 19:01:53 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Flink packaging makes life hard for SBT fat jar's From: Till Rohrmann To: user@flink.apache.org Content-Type: multipart/alternative; boundary=001a114af92ab7c4e4052c5fa09b --001a114af92ab7c4e4052c5fa09b Content-Type: text/plain; charset=UTF-8 Hi Shikhar, you're right that including a connector dependency would have let us spot the problem earlier. In fact, any project building a fat jar with SBT would have failed without setting the flink dependencies to provided. The problem is that the template is a general purpose template. Thus, it is also used for batch jobs. I fear that by including a connector in the default `build.sbt` file, many users will forget about it and simply include it in their job jars. I admit that I'm not totally consistent with my argumentation here because we're also including the `flink-scala` and `flink-streaming-scala` dependency per default. But I would like to keep the initial list of dependencies as lean as possible. What I've done, however, is to add testing SBT builds with a connector to our release testing tasks. This should catch similar problems which you've came across. Cheers, Till On Mon, Feb 22, 2016 at 6:20 PM, shikhar wrote: > Hi Till, > > Thanks so much for sorting this out! > > One suggestion, can the Flink template depend on a connector (Kafka?) -- > this would verify that assembly works smoothly for a very common use-case > when you need to include connector JAR's. > > Cheers, > > Shikhar > > > > -- > View this message in context: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-packaging-makes-life-hard-for-SBT-fat-jar-s-tp4897p5078.html > Sent from the Apache Flink User Mailing List archive. mailing list archive > at Nabble.com. > --001a114af92ab7c4e4052c5fa09b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Shikhar,

you're right that inclu= ding a connector dependency would have let us spot the problem earlier. In = fact, any project building a fat jar with SBT would have failed without set= ting the flink dependencies to provided.

The probl= em is that the template is a general purpose template. Thus, it is also use= d for batch jobs. I fear that by including a connector in the default `buil= d.sbt` file, many users will forget about it and simply include it in their= job jars. I admit that I'm not totally consistent with my argumentatio= n here because we're also including the `flink-scala` and `flink-stream= ing-scala` dependency per default. But I would like to keep the initial lis= t of dependencies as lean as possible.

What I'= ve done, however, is to add testing SBT builds with a connector to our rele= ase testing tasks. This should catch similar problems which you've came= across.

Cheers,
Till

On Mon, Feb 22, 2016 at = 6:20 PM, shikhar <shikhar@schmizz.net> wrote:
Hi Till,

Thanks so much for sorting this out!

One suggestion, can the Flink template depend on a connector (Kafka?) -- this would verify that assembly works smoothly for a very common use-case when you need to include connector JAR's.

Cheers,

Shikhar



--
View this message in context: http://apac= he-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-packaging-ma= kes-life-hard-for-SBT-fat-jar-s-tp4897p5078.html
Sent from the Apache Flink User Mai= ling List archive. mailing list archive at Nabble.com.

--001a114af92ab7c4e4052c5fa09b--