You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2010/06/03 01:01:56 UTC

[jira] Closed: (CASSANDRA-1151) For contrib modules that use Java, have a consistent build mechanism

     [ https://issues.apache.org/jira/browse/CASSANDRA-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Hanna closed CASSANDRA-1151.
-----------------------------------


> For contrib modules that use Java, have a consistent build mechanism
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-1151
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1151
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Contrib
>    Affects Versions: 0.6
>            Reporter: Jeremy Hanna
>            Assignee: Jeremy Hanna
>            Priority: Minor
>
> Contrib modules have a habit of periodically not working for some reason.  To some extent that's expected - they are optional contrib modules.  However, I think it's reasonable to at least have some way to perform a periodic sanity check on them if we can.
> This improvement would make sure there is a consistent build mechanism - build.xml - for each of the contrib modules that use Java.  That way, there could be a hudson build perhaps nightly or weekly, that could inform the devs if the contrib modules are not even compiling.  It's not like it would be a huge priority to fix immediately, but they would at least be aware that changes in the code/config have broken a contrib module.

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