You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Bret McGuire (Jira)" <ji...@apache.org> on 2025/12/05 03:55:00 UTC
[jira] [Commented] (CASSJAVA-119) Remove the binary tarball
[ https://issues.apache.org/jira/browse/CASSJAVA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042961#comment-18042961 ]
Bret McGuire commented on CASSJAVA-119:
---------------------------------------
Note: there's been a [fair amount of discussion|https://the-asf.slack.com/archives/C05LPRVNZV1/p1762413734922669] around the change to the source tarball for downloads on ASF Slack
> Remove the binary tarball
> -------------------------
>
> Key: CASSJAVA-119
> URL: https://issues.apache.org/jira/browse/CASSJAVA-119
> Project: Apache Cassandra Java driver
> Issue Type: Bug
> Components: Core
> Reporter: Bret McGuire
> Priority: Normal
>
> Our primary deployment mechanism is via Maven but we still make a tarball available via the [Cassandra downloads page|https://cassandra.apache.org/_/download.html]. For the Java driver this was originally downloading the binary tarball but we recently noticed that the contents of said binary tarball were (a) less than useful and (b) not even consistent across versions. As a result we've recently [changed this link|https://github.com/apache/cassandra-website/pull/304] to download the source tarball... meaning the binary tarball isn't really needed anymore.
>
> We should remove the infrastructure in the Maven build supporting the binary tarball. Basically if it isn't involved in creating the source tarball or artifacts for Maven Central we don't really need it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org