cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-380) Remove Groovy binary until we need to use it
Date Fri, 21 Aug 2009 12:35:15 GMT

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

Hudson commented on CASSANDRA-380:
----------------------------------

Integrated in Cassandra #174 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/174/])
    finish removing Groovy. patch by Michael Greene; reviewed by jbellis for 
remove groovy jar, half-baked Callout code.  patch by Michael Greene; reviewed by jbellis
for 


> Remove Groovy binary until we need to use it
> --------------------------------------------
>
>                 Key: CASSANDRA-380
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-380
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 0.4
>            Reporter: Michael Greene
>            Assignee: Michael Greene
>             Fix For: 0.4
>
>         Attachments: 380_v1.diff
>
>
> The Groovy JAR has been kept around for eventual callout support.  However, no one is
actively working on this task, and it is not slated for 0.4 (or 0.5 as far as I can tell).
 We should remove the JAR until it is needed, particularly since the Groovy project is advancing
much more quickly (the current JAR is severely outdated).  Also, it adds 2.2MB to a checkout.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message