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

Nick Bailey commented on CASSANDRA-4140:
----------------------------------------

bq. Wow, that's a definition of "hard" I'm unfamiliar with.

Hmm maybe I should have gone with confusing :). Plus I'm lazy. I don't want to 
wait for artifacts to build the javadoc AND then make 
build/dist/tools/stress/bin/stress executable so I can run it. C'mon, two whole 
extra steps!!??

Really though fixing that ^ was the spirit of this ticket. Moving stress was 
just a suggestion from irc. I would be fine if 'ant stress-build' put the built 
files in a place where tools/stress/bin/stress can find them.

Having said that I do think moving things like you mentioned into tools makes 
them less 'discoverable'. And moving stress would make it more 'discoverable'. 
                
> Move stress to main jar
> -----------------------
>
>                 Key: CASSANDRA-4140
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4140
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 1.2
>            Reporter: Nick Bailey
>            Priority: Trivial
>             Fix For: 1.2
>
>
> Right now its hard to run stress from a checkout of trunk. You need to do 
> 'ant artifacts' and then run the stress tool in the generated artifacts.
> A discussion on irc came up with the proposal to just move stress to the main 
> jar, but the stress/stressd bash scripts in bin/, and drop the tools 
> directory altogether. It will be easier for users to find that way and will 
> make running stress from a checkout much easier.

--
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