[
https://issues.apache.org/jira/browse/FLINK-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493737#comment-14493737
]
Robert Metzger commented on FLINK-1829:
---------------------------------------
Cool. I'm happy its not an issue with Flink directly (because the bug would be
part of the 0.9.0-milestone-1 release).
> Conflicting Jackson version in the Flink POMs
> ---------------------------------------------
>
> Key: FLINK-1829
> URL: https://issues.apache.org/jira/browse/FLINK-1829
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 0.9
> Reporter: Alexander Alexandrov
> Assignee: Robert Metzger
> Fix For: 0.9
>
>
> The current POM setup transitively includes multiple conflicting versions of
> the Jackson library over
> * {{com.amazonaws:aws-java-sdk}} (v. 2.1.1)
> * {{org.apache.avro:avro}} (v. 1.9.13)
> * {{org.apache.hbase:hbase-client}} (v. 1.8.8)
> When running jobs against a Flink local runtime embedded with:
> {code:xml}
> <dependency>
> <groupId>org.apache.flink</groupId>
> <artifactId>flink-scala</artifactId>
> <version>${flink.version}</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>org.apache.flink</groupId>
> <artifactId>flink-java</artifactId>
> <version>${flink.version}</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>org.apache.flink</groupId>
> <artifactId>flink-clients</artifactId>
> <version>${flink.version}</version>
> <scope>provided</scope>
> </dependency>
> {code}
> I get the following error:
> {noformat}
> 15-04-04 15:52:04 ERROR exception during creation
> akka.actor.ActorInitializationException: exception during creation
> at akka.actor.ActorInitializationException$.apply(Actor.scala:164)
> at akka.actor.ActorCell.create(ActorCell.scala:596)
> at akka.actor.ActorCell.invokeAll$1(ActorCell.scala:456)
> at akka.actor.ActorCell.systemInvoke(ActorCell.scala:478)
> at akka.dispatch.Mailbox.processAllSystemMessages(Mailbox.scala:279)
> at akka.dispatch.Mailbox.run(Mailbox.scala:220)
> at akka.dispatch.Mailbox.exec(Mailbox.scala:231)
> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
> at
> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at akka.util.Reflect$.instantiate(Reflect.scala:66)
> at akka.actor.ArgsReflectConstructor.produce(Props.scala:352)
> at akka.actor.Props.newActor(Props.scala:252)
> at akka.actor.ActorCell.newActor(ActorCell.scala:552)
> at akka.actor.ActorCell.create(ActorCell.scala:578)
> ... 9 more
> Caused by: java.lang.NoSuchMethodError:
> com.fasterxml.jackson.core.JsonFactory.requiresPropertyOrdering()Z
> at
> com.fasterxml.jackson.databind.ObjectMapper.<init>(ObjectMapper.java:445)
> at
> com.fasterxml.jackson.databind.ObjectMapper.<init>(ObjectMapper.java:366)
> at
> org.apache.flink.runtime.taskmanager.TaskManager.<init>(TaskManager.scala:134)
> ... 18 more
> {noformat}
> Fixing the Jackson version on the client side, e.g, with the following snippet
> {code:xml}
> <dependency>
> <groupId>com.fasterxml.jackson.core</groupId>
> <artifactId>jackson-core</artifactId>
> <version>2.2.1</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>com.fasterxml.jackson.core</groupId>
> <artifactId>jackson-databind</artifactId>
> <version>2.2.1</version>
> <scope>provided</scope>
> </dependency>
> <dependency>
> <groupId>com.fasterxml.jackson.core</groupId>
> <artifactId>jackson-annotations</artifactId>
> <version>2.2.1</version>
> <scope>provided</scope>
> </dependency>
> {code}
> solves the problem, but I guess it will be better if we can stick with one
> version in the build artifacts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
