[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
The goals of this task are:
* re-introduce the 'lib' artifact, with the same structure we had for the
older zookeeper 3.4.x ant generated artifact
* we should also add the LICENSE.txt file to the archive (it was missing from
the 3.4.x version tar.gz file)
* the new artifact should be generated only when the full-build profile is set
for maven
* we should also update the README_packaging.md file
was:
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
* The goals of this task are:
re-introduce the 'lib' artifact, with the same structure we had for the older
zookeeper 3.4.x ant generated artifact
* we should also add the LICENSE.txt file to the archive (it was missing from
the 3.4.x version tar.gz file)
* the new artifact should be generated only when the full-build profile is set
for maven
* we should also update the README_packaging.md file
> 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
> Time Spent: 1h
> Remaining Estimate: 0h
>
> During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was
> an artifact ({{zookeeper--lib.tar.gz}}) created just for the
> C-client, with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are generating a tarball during full-build then
> the C-client is not getting archived. In
> [PR-1078|https://github.com/apache/zookeeper/pull/1078]
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
* The goals of this task are:
re-introduce the 'lib' artifact, with the same structure we had for the older
zookeeper 3.4.x ant generated artifact
* we should also add the LICENSE.txt file to the archive (it was missing from
the 3.4.x version tar.gz file)
* the new artifact should be generated only when the full-build profile is set
for maven
* we should also update the README_packaging.md file
was:
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
* The goals of this task are:
re-introduce the 'lib' artifact, with the same structure we had for the older
zookeeper 3.4.x ant generated artifact
* we should also add the LICENSE.txt file to the archive (it was missing from
the 3.4.x version tar.gz file)
* the new artifact should be generated only when the full-build profile is set
for maven
* er should update the README_packaging.md file
> 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
> Time Spent: 50m
> Remaining Estimate: 0h
>
> During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was
> an artifact ({{zookeeper--lib.tar.gz}}) created just for the
> C-client, with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are generating a tarball during full-build then
> the C-client is not getting archived. In
> [PR-1078|https://github.com/apache/zookeeper/pull/1078] we
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
* The goals of this task are:
re-introduce the 'lib' artifact, with the same structure we had for the older
zookeeper 3.4.x ant generated artifact
* we should also add the LICENSE.txt file to the archive (it was missing from
the 3.4.x version tar.gz file)
* the new artifact should be generated only when the full-build profile is set
for maven
* er should update the README_packaging.md file
was:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
Note: we should also add the LICENSE.txt file to the archive (it was missing
from the 3.4.x version tar.gz file)
> 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
> Time Spent: 50m
> Remaining Estimate: 0h
>
> After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
> under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
> During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was
> an artifact ({{zookeeper--lib.tar.gz}}) created just for the
> C-client, with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
* The goals of this task are:
re-introduce the 'lib' artifact, with the same structure we had for the older
zookeeper 3.4.x ant generated artifact
* we should also add the LICENSE.txt file to the archive (it was missing from
the 3.4.x version tar.gz file)
* the new artifact should be generated only when the full-build profile is set
for maven
* er should update the README_packaging.md file
was:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
* The goals of this task are:
re-introduce the 'lib' artifact, with the same structure we had for the older
zookeeper 3.4.x ant generated artifact
* we should also add the LICENSE.txt file to the archive (it was missing from
the 3.4.x version tar.gz file)
* the new artifact should be generated only when the full-build profile is set
for maven
* er should update the README_packaging.md file
> 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
> Time Spent: 50m
> Remaining Estimate: 0h
>
> During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was
> an artifact ({{zookeeper--lib.tar.gz}}) created just for the
> C-client, with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are generating a
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
Note: we should also add the LICENSE.txt file to the archive (it was missing
from the 3.4.x version tar.gz file)
was:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
> 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
> Time Spent: 50m
> Remaining Estimate: 0h
>
> After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
> under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
> During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was
> an artifact ({{zookeeper--lib.tar.gz}}) created just for the
> C-client, with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are generating a tarball during full-build then
> the C-client is not getting archived. In
> [PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
> should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
> Note: we should also add the LICENSE.txt file to the archive (it was missing
> from the 3.4.x version tar.gz file)
--
This message was sent by Atlassian Jira
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build then
the C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
was:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build using
e.g. the {{mvn clean install -DskipTests -Pfull-build}} command, then the
C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
> under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
> During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was
> an artifact ({{zookeeper--lib.tar.gz}}) created just for the
> C-client, with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are generating a tarball during full-build then
> the C-client is not getting archived. In
> [PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
> should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was an
artifact ({{zookeeper--lib.tar.gz}}) created just for the C-client,
with the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build using
e.g. the {{mvn clean install -DskipTests -Pfull-build}} command, then the
C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
was:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder `zookeeper-client/zookeeper-client-c/target/c`.
During the old ZooKeeper 3.4 ant builds (`ant package-native`), there was an
artifact (`zookeeper--lib.tar.gz`) created just for the C-client, with
the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build using
e.g. the `mvn clean install -DskipTests -Pfull-build` command, then the
C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we should re-introduce
the `apache-zookeeper--lib.tar.gz` artifact.
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
> under the folder {{zookeeper-client/zookeeper-client-c/target/c}}.
> During the old ZooKeeper 3.4 ant builds ({{ant package-native}}), there was
> an artifact ({{zookeeper--lib.tar.gz}}) created just for the
> C-client, with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are generating a tarball during full-build
> using e.g. the {{mvn clean install -DskipTests -Pfull-build}} command, then
> the C-client is not getting archived. In
> [PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that we
> should re-introduce the {{apache-zookeeper--lib.tar.gz}} artifact.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[
https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mate Szalay-Beko updated ZOOKEEPER-3530:
Description:
After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
under the folder `zookeeper-client/zookeeper-client-c/target/c`.
During the old ZooKeeper 3.4 ant builds (`ant package-native`), there was an
artifact (`zookeeper--lib.tar.gz`) created just for the C-client, with
the following content:
{code:bash}
usr
|--- bin
|--- cli_mt
|--- cli_st
|--- load_gen
|--- include
|--- zookeeper
|--- proto.h
|--- recordio.h
|--- zookeeper.h
|--- zookeeper.jute.h
|--- zookeeper_log.h
|--- zookeeper_version.h
|--- lib
|--- libzookeeper_mt.a
|--- libzookeeper_mt.la
|--- libzookeeper_mt.so
|--- libzookeeper_mt.so.2
|--- libzookeeper_mt.so.2.0.0
|--- libzookeeper_st.a
|--- libzookeeper_st.la
|--- libzookeeper_st.so
|--- libzookeeper_st.so.2
|--- libzookeeper_st.so.2.0.0
{code}
Currently with maven, when we are generating a tarball during full-build using
e.g. the `mvn clean install -DskipTests -Pfull-build` command, then the
C-client is not getting archived. In
[PR-1078|https://github.com/apache/zookeeper/pull/1078] we should re-introduce
the `apache-zookeeper--lib.tar.gz` artifact.
was:
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 some binary tarball, just like it happened during the
older (3.4.x) ant builds.
in [PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that
the compiled C-client files should not end up in the
`apache-zookeeper--bin.tar.gz`file, but we should re-introduce the
`apache-zookeeper--lib.tar.gz` artifact containing the following files:
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> After ZOOKEEPER-3436 is merged, maven will build the C-client and put them
> under the folder `zookeeper-client/zookeeper-client-c/target/c`.
> During the old ZooKeeper 3.4 ant builds (`ant package-native`), there was an
> artifact (`zookeeper--lib.tar.gz`) created just for the C-client,
> with the following content:
> {code:bash}
> usr
> |--- bin
> |--- cli_mt
> |--- cli_st
> |--- load_gen
> |--- include
> |--- zookeeper
> |--- proto.h
> |--- recordio.h
> |--- zookeeper.h
> |--- zookeeper.jute.h
> |--- zookeeper_log.h
> |--- zookeeper_version.h
> |--- lib
> |--- libzookeeper_mt.a
> |--- libzookeeper_mt.la
> |--- libzookeeper_mt.so
> |--- libzookeeper_mt.so.2
> |--- libzookeeper_mt.so.2.0.0
> |--- libzookeeper_st.a
> |--- libzookeeper_st.la
> |--- libzookeeper_st.so
> |--- libzookeeper_st.so.2
> |--- libzookeeper_st.so.2.0.0
> {code}
> Currently with maven, when we are generating a tarball during full-build
> using e.g. the `mvn clean install -DskipTests -Pfull-build` command, then the
> C-client is not getting archived. In
> [PR-1078|https://github.com/apache/zookeeper/pull/1078] we should
> re-introduce the `apache-zookeeper--lib.tar.gz` artifact.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Szalay-Beko updated ZOOKEEPER-3530: Description: 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 some binary tarball, just like it happened during the older (3.4.x) ant builds. in [PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that the compiled C-client files should not end up in the `apache-zookeeper--bin.tar.gz`file, but we should re-introduce the `apache-zookeeper--lib.tar.gz` artifact containing the following files: was: 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. > 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 > Time Spent: 0.5h > Remaining Estimate: 0h > > 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 some binary tarball, just like it happened during the > older (3.4.x) ant builds. > in [PR-1078|https://github.com/apache/zookeeper/pull/1078] we discussed that > the compiled C-client files should not end up in the > `apache-zookeeper--bin.tar.gz`file, but we should re-introduce the > `apache-zookeeper--lib.tar.gz` artifact containing the following > files: -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ZOOKEEPER-3530) Include compiled C-client in the binary tarball
[ 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)
