That's incorrect; you need to do the same for filesystems, as one
example. So, build everything -> build filesystems -> build flink-dist.
On 03/07/2020 14:31, Robert Metzger wrote:
We could also build releases by calling "mvn package" again in
"flink-dist". But all these solutions are far from
We could also build releases by calling "mvn package" again in
"flink-dist". But all these solutions are far from elegant.
Ideally the Maven folks have implemented something nicer by now. Let's see
what they say.
On Fri, Jul 3, 2020 at 1:20 PM Chesnay Schepler wrote:
> It's not that *difficult
It's not that /difficult /for us to work around it mind you; we "just"
have to
a) separate the distribution packaging from the flink-dist jar from the
distribution assembly, so we can have dependencies on the various
opt/plugins modules without pulling in dependencies into the flink-dist jar,
I just reached out to the users@maven mailing list again to check if
there's any resolution for shading behavior post 3.2.5 [1]
[1]
https://lists.apache.org/thread.html/8b2dcf462de814d06d8e30bafce2c886217c5790a3ee07d33d0b8dfc%40%3Cusers.maven.apache.org%3E
On Thu, Jun 4, 2020 at 3:08 PM Chesnay
You don't necessarily need to use maven 3.2.5, you just have to know
what to watch out for.
For that reason we are _not_ forcing maven 3.2.5 in general, but for
releases only to be on the safe side.
Some time ago Gradle was brought up as a potential replacement for
maven, and I'd like to see t
