You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Greene (JIRA)" <ji...@apache.org> on 2009/08/19 18:31:15 UTC
[jira] Created: (CASSANDRA-380) Remove Groovy binary until we need
to use it
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
Fix For: 0.4
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.
[jira] Commented: (CASSANDRA-380) Remove Groovy binary until we
need to use it
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745573#action_12745573 ]
Michael Greene commented on CASSANDRA-380:
------------------------------------------
Sorry, will follow .sh advice next time, this should also be done:
{{{
svn rm --force src/java/org/apache/cassandra/procedures
}}}
> 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.
[jira] Commented: (CASSANDRA-380) Remove Groovy binary until we
need to use it
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745506#action_12745506 ]
Michael Greene commented on CASSANDRA-380:
------------------------------------------
The patch gets rid of all the Callout classes. The diff to 0 issue is there, as you mention.
After applying the patch the following will clean up the empty files:
{{{
svn rm --force src/java/org/apache/cassandra/db/CalloutDeployMessage.java
svn rm --force src/java/org/apache/cassandra/db/CalloutDeployVerbHandler.java
svn rm --force src/java/org/apache/cassandra/db/CalloutManager.java
}}}
> 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
> 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.
[jira] Commented: (CASSANDRA-380) Remove Groovy binary until we
need to use it
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745575#action_12745575 ]
Jonathan Ellis commented on CASSANDRA-380:
------------------------------------------
also committed, thanks
> 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.
[jira] Commented: (CASSANDRA-380) Remove Groovy binary until we
need to use it
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745499#action_12745499 ]
Jonathan Ellis commented on CASSANDRA-380:
------------------------------------------
this leaves a bunch of Callout* classes. Shouldn't we make a clean sweep of it?
> 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
> 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.
[jira] Commented: (CASSANDRA-380) Remove Groovy binary until we
need to use it
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745500#action_12745500 ]
Jonathan Ellis commented on CASSANDRA-380:
------------------------------------------
btw it is easier to apply a .sh that does svn rm's, since the diff just patches it down to zero
> 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
> 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.
[jira] Commented: (CASSANDRA-380) Remove Groovy binary until we
need to use it
Posted by "Bill de hOra (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745184#action_12745184 ]
Bill de hOra commented on CASSANDRA-380:
----------------------------------------
+1.
> 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
> Fix For: 0.4
>
>
> 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.
[jira] Commented: (CASSANDRA-380) Remove Groovy binary until we
need to use it
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-380) Remove Groovy binary until we need
to use it
Posted by "Michael Greene (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Greene updated CASSANDRA-380:
-------------------------------------
Attachment: 380_v1.diff
Patch removes groovy lib, associated license information, and all callout structures. Future callout development can reference this change or start from scratch.
> 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
> 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.