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

Jonathan Ellis commented on CASSANDRA-3507:
-------------------------------------------

If we distribute the jar it has to go in lib/ with a license, no Maven 
shortcuts.
                
> Proposal: separate cqlsh from CQL drivers
> -----------------------------------------
>
>                 Key: CASSANDRA-3507
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3507
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Packaging, Tools
>    Affects Versions: 1.0.3
>         Environment: Debian-based systems
>            Reporter: paul cannon
>            Assignee: paul cannon
>            Priority: Blocker
>              Labels: cql, cqlsh
>             Fix For: 1.0.7
>
>
> Whereas:
> * It has been shown to be very desirable to decouple the release cycles of 
> Cassandra from the various client CQL drivers, and
> * It is also desirable to include a good interactive CQL client with releases 
> of Cassandra, and
> * It is not desirable for Cassandra releases to depend on 3rd-party software 
> which is neither bundled with Cassandra nor readily available for every 
> target platform, but
> * Any good interactive CQL client will require a CQL driver;
> Therefore, be it resolved that:
> * cqlsh will not use an official or supported CQL driver, but will include 
> its own private CQL driver, not intended for use by anything else, and
> * the Cassandra project will still recommend installing and using a proper 
> CQL driver for client software.
> To ease maintenance, the private CQL driver included with cqlsh may very well 
> be created by "copying the python CQL driver from one directory into 
> another", but the user shouldn't rely on this. Maybe we even ought to take 
> some minor steps to discourage its use for other purposes.
> Thoughts?

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