cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3665) [patch] allow for clientutil.jar to be used without the base cassandra.jar for client applications
Date Fri, 27 Apr 2012 15:00:48 GMT


Eric Evans commented on CASSANDRA-3665:

bq. remove the dependency on commons_lang for clientutils for something silly.

This one is applied, thanks.

As for the one meant to support {{UUIDGen.getTimeUUIDBytes()}}, make sure you are using {{ant
test-clientutil-jar}} when you test.  That target has been setup to _only_ include the dependencies
we're expecting, and nothing else.  That test fails with your other patches because, as I
mentioned elsewhere, {{FBUtilities}} is a quagmire that requires pulling in many new dependencies.

I'm going to go ahead and close this issue, since the original scope has been met.  If you
come up with a strategy to better support the non-essential parts of UUIDGen, or to further
disentangle the dependencies, feel free to reopen it, or better yet open another, more specific
> [patch] allow for clientutil.jar to be used without the base cassandra.jar for client
> --------------------------------------------------------------------------------------------------
>                 Key: CASSANDRA-3665
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.0.8
>            Reporter: Dave Brosius
>            Assignee: Eric Evans
>            Priority: Minor
>             Fix For: 1.0.10
>         Attachments: fail_client_utils_test.diff, fix_client_util_jar.diff, remove_commons_lang_dep.diff,
v1-0001-CASSANDRA-3665-test-to-expose-missing-dependencies.txt, v1-0002-eliminate-dependency-on-FBUtilities.txt
> clientutil.jar can't be run from a client by itself without the presence of cassandra.jar
which seems wrong. Added needed classes to run by itself.

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