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/02 17:59:39 UTC
[jira] Created: (CASSANDRA-1151) For contrib modules that use Java,
have a consistent build mechanism
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.
[jira] Closed: (CASSANDRA-1151) For contrib modules that use Java,
have a consistent build mechanism
Posted by "Jeremy Hanna (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-1151) For contrib modules that use
Java, have a consistent build mechanism
Posted by "Johan Oskarsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875005#action_12875005 ]
Johan Oskarsson commented on CASSANDRA-1151:
--------------------------------------------
Still, it wouldn't hurt with a somewhat general build framework for them. If we could kick off a build of all java based contrib modules from the main build.xml that could be included in Hudson. That way we would at least know if a contrib is failing to build and can create a ticket. Hadoop has something like this and it has worked out quite well.
> 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.
[jira] Commented: (CASSANDRA-1151) For contrib modules that use
Java, have a consistent build mechanism
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874949#action_12874949 ]
Jonathan Ellis commented on CASSANDRA-1151:
-------------------------------------------
OTOH the point of accepting those in-tree is to say, "this is of enough interest that we are willing to take some responsibility for maintaining this."
> 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.
[jira] Resolved: (CASSANDRA-1151) For contrib modules that use
Java, have a consistent build mechanism
Posted by "Jeremy Hanna (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna resolved CASSANDRA-1151.
-------------------------------------
Resolution: Not A Problem
Contrib modules really are unofficial and should have their own stewards - those who contributed them in the first place.
> 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.