Parent: #1
Summary
Make the version-specific thin JARs releasable and operable on Cassandra nodes without repackaging Cassandra itself.
Implementation plan
- Publish one clearly named artifact per supported release line.
- Generate checksums, signatures, SBOMs, dependency/license notices, and reproducible build metadata.
- Verify release artifacts contain no Cassandra server classes or runtime JARs.
- Document:
- tarball, Debian, and RPM-style Cassandra layouts;
- required Cassandra and Java patch ranges;
--cassandra-home/--cassandra-conf/--java-home;
- workspace placement and disk sizing;
- snapshot/backup input requirements;
- loopback ports and cqlsh connection;
- delta/snapshot export and supported production import procedures;
- crash recovery and cleanup;
- classpath/linkage troubleshooting.
- Provide a preflight-only command suitable for deployment automation.
- Provide a release compatibility manifest consumable by the bootstrap.
- Make warnings explicit that the tool never targets the live Cassandra JVM/data directory.
Acceptance criteria
Dependencies
Depends on #2, #3, #8, #9, #10, and #11.
Design
See sections 7.2, 7.3, 14, and 19 of docs/cql-mutation-workspace-design.md.
Parent: #1
Summary
Make the version-specific thin JARs releasable and operable on Cassandra nodes without repackaging Cassandra itself.
Implementation plan
--cassandra-home/--cassandra-conf/--java-home;Acceptance criteria
Dependencies
Depends on #2, #3, #8, #9, #10, and #11.
Design
See sections 7.2, 7.3, 14, and 19 of
docs/cql-mutation-workspace-design.md.