[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ZOOKEEPER-3530:
--------------------------------------
Labels: pull-request-available (was: )
> Include compiled C-client in the binary tarball
> -----------------------------------------------
>
> Key: ZOOKEEPER-3530
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3530
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.6.0, 3.5.7
> Reporter: Mate Szalay-Beko
> Assignee: Mate Szalay-Beko
> Priority: Major
> Labels: pull-request-available
>
> After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
> under the folder `zookeeper-client/zookeeper-client-c/target/c`.
> When we are generating a tarball during full-build using e.g. the `mvn clean
> install -DskipTests -Pfull-build` command, then we would expect the compiled
> C-client to end up in the binary tarball, just like it happened during the
> older (3.4.x) ant builds.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
