Re: Return of Flink shading problems in 1.2.0

2017-03-20 Thread Robert Metzger
;> >> >> >> *From: *"Foster, Craig" >> *Reply-To: *"user@flink.apache.org" >> *Date: *Friday, March 17, 2017 at 7:23 AM >> *To: *"user@flink.apache.org" >> *Cc: *Ufuk Celebi , Robert Metzger , >> Stephan Ewen >&

Re: Return of Flink shading problems in 1.2.0

2017-03-20 Thread Robert Metzger
know of a new workaround for 3.3.x. > > > > Thanks! > > Craig > > > > *From: *"Foster, Craig" > *Reply-To: *"user@flink.apache.org" > *Date: *Friday, March 17, 2017 at 7:23 AM > *To: *"user@flink.apache.org" > *Cc: *Ufuk Celebi , Robe

Re: Return of Flink shading problems in 1.2.0

2017-03-17 Thread Foster, Craig
: Ufuk Celebi , Robert Metzger , Stephan Ewen Subject: Re: Return of Flink shading problems in 1.2.0 Hey Stephen: I am building twice in every case described in my previous mail. Well, building then rebuilding the flink-dist submodule. This was fixed in BigTop but I started seeing this issue

Re: Return of Flink shading problems in 1.2.0

2017-03-17 Thread Foster, Craig
Hey Stephen: I am building twice in every case described in my previous mail. Well, building then rebuilding the flink-dist submodule. This was fixed in BigTop but I started seeing this issue again with Flink 1.2.0. I was wondering if there's something else in the environment that could prevent

Re: Return of Flink shading problems in 1.2.0

2017-03-17 Thread Stephan Ewen
Hi Craig! Maven 3.3.x has a shading problem. You need to build two times, once from root, once inside "flink-dist". Have a look here: https://ci.apache.org/projects/flink/flink-docs-release-1.2/setup/building.html#dependency-shading Maybe that way missed in BigTop? I am wondering if we should a

Re: Return of Flink shading problems in 1.2.0

2017-03-17 Thread Ufuk Celebi
Pulling in Robert and Stephan who know the project's shading setup the best. On Fri, Mar 17, 2017 at 6:52 AM, Foster, Craig wrote: > Hi: > > A few months ago, I was building Flink and ran into shading issues for > flink-dist as described in your docs. We resolved this in BigTop by adding > the co