[
https://issues.apache.org/jira/browse/CASSANDRA-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875637#action_12875637
]
Jeremy Hanna commented on CASSANDRA-1159:
-----------------------------------------
Maybe having unlinked build.xml files would be a way to keep them separate.
Then in Hudson they could be run separately from any regular core build - as a
contrib build plan. That could be run nightly and separate from the core build.
Just make it a sanity check?
Would that be separate enough to keep it simply a heads up for build errors in
those modules?
If we ever do get things that are completely separate from the core but we want
to make sure they're stable, then at that point we could add them as spin-off
builds in the core's build.xml...?
> 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
> Assignee: Jeremy Hanna
> Priority: Minor
> Fix For: 0.7
>
>
> 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.
