Managing libraries for Cassandra is a bit less straight forward compared to other projects, as the build process is based on ant, maven and manually managed jars. Make sure to follow the steps below carefully and pay attention to any emerging issues in the Jenkins CI Environment and reported related issues on Jira/ML, in case of any project dependency changes.
As Cassandra is an Apache product, all included libraries must follow Apache’s software license requirements.
lib
directorylib/license
filesbuild.xml
parent-pom
with correct versionall-pom
if simple Cassandra dependency (see below)ant build
compile target. Listed dependenices will be resolved and copied to build/lib/{jar,sources}
by executing the maven-ant-tasks-retrieve-build
target. This should contain libraries that are required for build tools (grammar, docs, instrumentation), but are not shipped as part of the Cassandra distribution.maven-ant-tasks-retrieve-test
to retrieve and save dependencies to build/test/lib
. Exclusively used during JUnit test execution.ant publish
ant artifacts
. Should be left as is, but needed for installing or deploying releases.Here are some useful commands that may help you out resolving conflicts.
ant realclean
- gets rid of the build directory, including build artifacts.mvn dependency:tree -f build/apache-cassandra-*-SNAPSHOT.pom -Dverbose -Dincludes=org.slf4j
- shows transitive dependency tree for artifacts, e.g. org.slf4j. In case the command above fails due to a missing parent pom file, try running ant mvn-install
.rm ~/.m2/repository/org/apache/cassandra/apache-cassandra/
- removes cached local Cassandra maven artifacts