cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3300) relocate Java (JDBC) CQL driver
Date Thu, 13 Oct 2011 09:13:11 GMT


Stephen Connolly commented on CASSANDRA-3300:

is my mavenized version.

Brief summary of the changes

    * Using cassandra-maven-plugin to start a cassandra server for running the integration
    * Using build-helper-maven-plugin and resource filtering to ensure that the tests run
on random ports each time
    * Using maven-failsafe-plugin so that integration tests are run while the cassandra server
is running.
    * No need for the lib directory any more

Note, before you can build this you need to get cassandra-clientutils.jar into your local

  mvn install:install-file \
    -DgroupId=org.apache.cassandra \
    -DartifactId=cassandra-clientutil \
    -Dversion=1.0.0-rc2-SNAPSHOT \
    -Dpackaging=jar \

Then to run the whole build including integration tests

  mvn clean install

To just create the jars

  mvn package -DskipTests

Once we sort out promotion through, making a release should be just

  mvn release:prepare release:perform

And then close and release the staging repo at (same GUI as
> relocate Java (JDBC) CQL driver
> -------------------------------
>                 Key: CASSANDRA-3300
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>          Components: Drivers
>            Reporter: Eric Evans
>            Priority: Minor
>              Labels: cql
>         Attachments: v1-0001-CASSANDRA-3300-remove-driver-build-test.txt
> A new project as been created at,
a current snapshot of the code from trunk has been imported, and the tests updated.
> I've configured commit notifications to be sent to, though
this can be changed if people object.
> To the best of my knowledge, the only thing remaining is to configure the initial set
of committers and admins.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message