Github user markreddy commented on the pull request:
https://github.com/apache/flink/pull/2003#issuecomment-220307660
I took a look at the root issue of upgrading to 2.19.1. I'm able to
reliably reproduce this issue on my laptop.
When I bump the version I get the same as @tillrohrmann
`java.lang.NoSuchMethodError:
org.apache.flink.runtime.util.ZooKeeperUtils.startCuratorFramework(Lorg/apache/flink/configuration/Configuration;)Lorg/apache/curator/framework/CuratorFramework`
When running the build in debug mode for both 2.18.1 and 2.19.1 I observed
some differences in the classpath.
**2.18.1**
`[DEBUG] boot(compact) classpath: surefire-booter-2.18.1.jar
surefire-api-2.18.1.jar test-classes classes
flink-core-1.1-SNAPSHOT.jar.....`
**2.19.1**
`[DEBUG] boot(compact) classpath: surefire-booter-2.19.1.jar
surefire-api-2.19.1.jar test-classes flink-runtime_2.10-1.1-SNAPSHOT.jar
flink-core-1.1-SNAPSHOT.jar.....`
So 2.19.1 has changed behaviour. What is loaded onto the classpath differs,
in 2.19.1 instead of loading target/classes it loads the actual built jar.
https://issues.apache.org/jira/browse/SUREFIRE-855 confirms this.
The issue with this is the final jar has curator shaded while the test
classes are looking for the unshaded version of curator, as shown by the debug
output:
`Lorg/apache/curator/framework/CuratorFramework`
If @mxm can get everything working on a lower version thats the easiest
solution. If not or we want to proceed with moving up in version, at least we
know the root of the issue and can work from there....
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
