You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/04/11 18:04:12 UTC
[jira] [Resolved] (CASSANDRA-1159) For contrib modules that use
Java, have a consistent build mechanism
[ https://issues.apache.org/jira/browse/CASSANDRA-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-1159.
---------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 0.8)
See CASSANDRA-1805 for refactoring contrib.
> For contrib modules that use Java, have a consistent build mechanism
> --------------------------------------------------------------------
>
> Key: CASSANDRA-1159
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1159
> Project: Cassandra
> Issue Type: Improvement
> Components: Contrib
> Reporter: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira