[
https://issues.apache.org/jira/browse/MESOS-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16084726#comment-16084726
]
Andrew Schwartzmeyer commented on MESOS-5905:
---------------------------------------------
You know, this issue implies that we build the ZooKeeper tests in the first
place in CMake. But we do not. I wish I had your branch Srinivas! I just
reinvented it, and this is precisely my current problem. I'm just going to...
fix it.
> Zookeeper tests do not work on CMake builds as directory structure changed.
> ---------------------------------------------------------------------------
>
> Key: MESOS-5905
> URL: https://issues.apache.org/jira/browse/MESOS-5905
> Project: Mesos
> Issue Type: Bug
> Components: build
> Affects Versions: 1.1.0
> Reporter: Srinivas
> Assignee: Andrew Schwartzmeyer
>
> Zookeeper tests load the class path at runtime. The zookeepers' SetUpTestCase
> uses the zookeeper build directory to extract the required jars into the java
> classpath for tests to work. This will break with cmake builds as there is
> extra build path generated when using cmake. The new make directory looks
> like "3rdparty/zookeeper-3.4.8/src/zookeeper-3.4.8" instead of
> "3rdparty/zookeeper-3.4.8". SetupTestCase should handle this. Although there
> is build setting to specify "ZOOKEEPER_VERSION" there is no build flag to
> specify zookeeper install directory and that information is deduced.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
