[ 
http://jira.amdatu.org/jira/browse/AMDATU-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bram de Kruijff resolved AMDATU-272.
------------------------------------

      Assignee: Ivo Ladage - van Doorn  (was: Bram de Kruijff)
    Resolution: Fixed

For the record. I feel we should not be including this kind of tooling just for 
some "ease of configuration" that still requires people to svn checkout, modify 
poms etc etc. This is an external tool that can be dowloaded and used of the 
shell. Adding it to our codebase brings the burden of maintining, documenting 
and supporting it. Having said so.. it is in there and it is not in the way or 
in any critical part of our runtime. Therefore I'm not going to block a release 
on it. Case closed (for now)

> Distribute cassandra tooling with Amdatu
> ----------------------------------------
>
>                 Key: AMDATU-272
>                 URL: http://jira.amdatu.org/jira/browse/AMDATU-272
>             Project: Amdatu
>          Issue Type: Improvement
>          Components: Amdatu Cassandra
>    Affects Versions: 0.1.0
>            Reporter: Ivo Ladage - van Doorn
>            Assignee: Ivo Ladage - van Doorn
>             Fix For: 0.1.0
>
>
> It would be a good idea to distribute cassandra tooling with Amdatu. Tooling 
> like cassandra-cli and nodetool for example, which are part of the usual 
> cassandra bin but not included in the cassandra application osgi bundle. This 
> tooling is necessary for example for cluster management. Amdatu should also 
> provide the possibility to configure the properties necessary to use the 
> tooling, like JMX settings.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to