Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0DD54200C63 for ; Thu, 11 May 2017 20:32:24 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0C780160BC7; Thu, 11 May 2017 18:32:24 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 532DC160BB3 for ; Thu, 11 May 2017 20:32:23 +0200 (CEST) Received: (qmail 46348 invoked by uid 500); 11 May 2017 18:32:22 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 46337 invoked by uid 99); 11 May 2017 18:32:22 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 May 2017 18:32:22 +0000 Received: from mail-pg0-f52.google.com (mail-pg0-f52.google.com [74.125.83.52]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3084D1A031E for ; Thu, 11 May 2017 18:32:22 +0000 (UTC) Received: by mail-pg0-f52.google.com with SMTP id f131so3882540pgc.2 for ; Thu, 11 May 2017 11:32:22 -0700 (PDT) X-Gm-Message-State: AODbwcAcZmK34KoFMf+SE/xr9agSzy7jWimxPoiAeCRh/RLVHOUAejlW fcGQ1c6oIl4W1jgi1Ieo0Pp0Dko9/g== X-Received: by 10.98.15.23 with SMTP id x23mr197207pfi.86.1494527541762; Thu, 11 May 2017 11:32:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.131.67 with HTTP; Thu, 11 May 2017 11:32:06 -0700 (PDT) In-Reply-To: References: <997c685c-d95b-b796-a183-a22d6d384946@apache.org> From: Stephan Ewen Date: Thu, 11 May 2017 20:32:06 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] Changing Flink's shading model To: "dev@flink.apache.org" Content-Type: multipart/alternative; boundary=001a11437a523be115054f43cfe1 archived-at: Thu, 11 May 2017 18:32:24 -0000 --001a11437a523be115054f43cfe1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable @eron I would try to rely almost purely on the shade plugin On Thu, May 11, 2017 at 7:53 PM, Eron Wright wrote: > In my opinion, the ideal approach to mitigating conflicts between > application code and Flink itself is to relocate all of Flink's > dependencies. Rationale is to avoid placing the burden of relocation on > the app developer, and ultimately to eliminate the need for an app > uber-jar. > > For example, imagine enhancing Flink to directly support Maven > repositories, e.g. > ``` > $ flink run --package org.example:app:1.0 > ... > Downloading: https://repo1.maven.org/maven2/org/example/app/1.0/app.pom > ... > ``` > > From that perspective, FLINK-6529 is another good step in that direction. > But it seems like we'd be forking more libraries ("fetty"!). Would we > need to alter the source code or rely on the shading plugin? As Chesnay > mentioned, what's the impact in the IDE? > > In the future, could the entire flink-runtime be made an uber-jar, > performing the relocation at that stage? > > > On Thu, May 11, 2017 at 3:36 AM, Ufuk Celebi wrote: > > > On Thu, May 11, 2017 at 10:59 AM, Till Rohrmann > > wrote: > > > Have we somewhere documented how to publish > > > artifacts on Maven central? > > > > Pulling in Robert who published frocks. @Robert: Would you like to > > volunteer for this? Would really help to combine this with some docs > > about publishing Maven artefacts in the flink-shaded-deps README. :-) > > In general, I'm curious to hear your opinion on this proposal. > > > > =E2=80=93 Ufuk > > > --001a11437a523be115054f43cfe1--