Ah of course. That did the trick, thank you.
Stephan Ewen schrieb am Fri Nov 14 2014 at 14:46:51:
> I think that basically destroys the guava shading, because the guava
> classes are not in "com.google.guava", rather than in "com.google.common"
> and "com.google.thirdparty"...
>
> The excludes y
I think that basically destroys the guava shading, because the guava
classes are not in "com.google.guava", rather than in "com.google.common"
and "com.google.thirdparty"...
The excludes you defined refer to what code goes into the shaded jar, not
what is relocated. If you define the excludes in t
Thanks for your answer.
I did already take a look at the documentation. We have the following code
snippet in our pom in flink-shade.
com.google.guava:guava
com.google
org.apache.flink.shaded.com.google
I first thought that the includes specify a whitelist of the packages to be
relocated
Hey Sebastian!
I think there are two approaches:
- You can either shade the protobuf Classes as well
- or you can exclude the ptotobuf namespace from shading. Have a look at
the shade plugin docs.
Stephan
Am 14.11.2014 09:49 schrieb "Sebastian Kunert" :
> Hi Guys,
>
> I am currently worki
Hi Guys,
I am currently working on integrating Flink with Mesos. Therefore I
currently reuse the flink-yarn uberjar assembly to build a jar that
contains all the classes I need. Now I have a dependency on a Google
Protobuf class. I added protobuf as a dependency to my module and it is
also contain
