+1, we definitely need to start releasing jars, and preferrably doing it with
some reasonable cadence / on demand.
There is a slight problem with the fact we can not cut releases without votes,
which, combined with the fact that we need sha-stable snapshots, makes it
tricky. Best way to do this so far I could come up with is to just add short
SHA as a snapshot prefix. This way no-one will override it by accident at least.
Meanwhile, since it'll take a bit of time to set everything up, there is a
quick and easy way to do this, which is essentially what we do in Harry, if
anyone needs this urgently:
if [ -z "${CASSANDRA_REPO}" ]; then
CASSANDRA_REPO="g...@github.com:apache/cassandra.git"
fi
git clone -b trunk ${CLONE_REPO} cassandra
cd cassandra
./build-shaded-dtest-jar.sh
Script will also output the version it installs to local maven.
On Tue, Nov 28, 2023, at 8:02 PM, Abe Ratnofsky wrote:
> Hey folks - wanted to raise a separate thread to discuss publishing of
> dtest-shaded JARs on release.
>
> Currently, adjacent projects that want to use the jvm-dtest framework need to
> build the shaded JARs themselves. This is a decent amount of work, and is
> duplicated across each project. This is mainly relevant for projects like
> Sidecar and Driver. Currently, those projects need to clone and build
> apache/cassandra themselves, run ant dtest-jar, and move the JAR into the
> appropriate place. Different build systems treat local JARs differently, and
> the whole process can be a bit complicated. Would be great to be able to
> treat these as normal dependencies.
>
> https://issues.apache.org/jira/browse/CASSANDRA-19113
>
> Any objections?
>
> --
> Abe
