[ 
https://issues.apache.org/jira/browse/CASSANDRA-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244629#comment-13244629
 ] 

Eric Evans commented on CASSANDRA-3665:
---------------------------------------

For what it's worth, and whether or not it's Right, this was more or less 
intentional.  The only dependencies added were those needed by the classes in 
{{o.a.c.cql.jdbc}}. {{UUIDGen}} is an example of something that was added as a 
dependency (not to be used directly), and the only transient dependencies 
included were those needed by the methods the Jdbc* classes access.

TL;DR, that jar hasn't been setup to use {{UUIDGen.getTimeUUIDBytes()}}.

I realize that's probably not at all obvious though, so we should probably come 
up with a better solution (and open a separate ticket).

Unfortunately, simply including {{FBUtilities}} is non-trivial because that 
results in mountains of transient dependencies being pulled in.  I think we'll 
either need to refactor our way around {{FBUtilities}}, or split up {{UUIDGen}}.
                
> [patch] allow for clientutil.jar to be used without the base cassandra.jar 
> for client applications
> --------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3665
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3665
>             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, 
> 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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to