Hi Martin!
It looks like your project added a rule to not allow a higher netty.io
version. Any specific reason that the rule was added? Would be good to
understand that, because the rule stands in conflict with Flink's
dependencies.
Flink internally has multiple uses of netty: Akka remote, Flink
Its using a maven-enforcer-plugin (see config below). The project itself
does not use netty.
I just discovered that I still compile fine from within IntelliJ I just
cannot built it externally with maven (which I need to package the jar to
deploy on Yarn).
cheers Martin
maven-enforcer-plugin
Hi Martin.
can you try to exclude the netty dependency from your Flink dependencies?
Another approach would be to disable the check, or add an exception to it ;)
Why did you add the check in the first place?
On Wed, Jan 20, 2016 at 2:13 PM, Martin Neumann wrote:
> Its using
Hi,
I have a weird problem. Yesterday I had to clean my local maven cache for a
different application.
Since afterwards one of my Flink streaming jobs does not compile anymore. I
didn't change any code just made maven pull all dependencies again.
I'm totally stomped by this, please help me!
Hi Martin,
is the logproc-flink project using the maven-enforcer-plugin to enforce a
minimum version of netty?
We recently downgraded (a minor version) of netty because of an issue.
Maybe that's the issue.
Can you check the enforcer rules of your project?
On Wed, Jan 20, 2016 at 1:48 PM, Martin
Its a fork of a different project, so I didn't add it myself. I disabled it
for now and so far it works, I will try to find out why it was there in the
first place and if necessary find a workaround.
thanks for the help
Martin
On Wed, Jan 20, 2016 at 2:32 PM, Robert Metzger