[
https://issues.apache.org/jira/browse/CASSANDRA-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777557#action_12777557
]
Dirk Weber edited comment on CASSANDRA-549 at 11/13/09 4:56 PM:
----------------------------------------------------------------
Now all jars within the lib-directory will be added dynamically to the
classpath of the cli-client. So you shouldn't have to touch the batch-file when
you change the dependencies of the project.
But you still have to set CASSANDRA_HOME. Not quite sure how to avoid this: the
existing script to start cassandra server on windows (bin\cassandra.bat) tries
to set the path-variable automatically, but for some reason this doesn't seem
to work on my machine. I can just start the server when I set the environment
variable manually.
was (Author: dirk_weber):
Now all jars within the lib-directory will be added dynamically to the
classpath of the cli-client. So you shouldn't have to touch the batch-file when
you change the dependencies of the project.
> Windows start script for cli client
> -----------------------------------
>
> Key: CASSANDRA-549
> URL: https://issues.apache.org/jira/browse/CASSANDRA-549
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Affects Versions: 0.4
> Environment: MS Windows
> Reporter: Dirk Weber
> Priority: Minor
> Attachments: startClient.bat
>
>
> There should be a windows start-script for the command-line-interface client.
> Up to now there is just such a script for linux-systems (in folder
> bin\cassandra-cli)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
