[
https://issues.apache.org/jira/browse/CASSANDRA-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876310#action_12876310
]
Jeremy Hanna edited comment on CASSANDRA-1159 at 6/7/10 1:24 PM:
-----------------------------------------------------------------
There was some talk in the IRC channel about just renaming the contrib
directory to examples and like Jonathan mentioned, drawing that line to only
include examples. Is that going to suffice?
Examples would potentially include:
* bmt_example - possibly renamed to bulk_loader
* client_only - possibly renamed to fat_client
* word_count
* pig - once pig is in core, we can just have the example script in examples,
but we're waiting for pig 0.7.0 to be added to a public mvn repo (PIG-1334)
So if there is only <cassandra>/examples, where would circuit and py_stress go?
Would javautils go in the same place, possibly renamed to something more
descriptive of what it does, provides a fresh data environment from what it
looks like?
I suppose we could have contrib/examples and contrib/utilities but that's kind
of heavy. Otherwise we could just have <cassandra>/examples and
<cassandra>/utilities.
We're deleting contrib/maven?
In any case - I can make sure that we have a build.xml file for each of the
examples.
was (Author: jeromatron):
There was some talk in the IRC channel about just renaming the contrib
directory to examples and like Jonathan mentioned, drawing that line to only
include examples. Is that going to suffice?
Examples would potentially include:
* bmt_example - possibly renamed to bulk_loader
* client_only - possibly renamed to fat_client
* word_count
* pig - once pig is in core, we can just have the example script in examples,
but we're waiting for pig 0.7.0 to be added to a public mvn repo (PIG-1334)
So if there is only <cassandra>/examples, where would circuit and py_stress go?
Would javautils go in the same place, possibly renamed to something more
descriptive of what it does, provides a fresh data environment from what it
looks like?
I suppose we could have contrib/examples and contrib/utilities but that's kind
of heavy. Otherwise we could just have <cassandra>/examples and
<cassandra>/utilities.
We're deleting contrib/maven?
Once we decide on this - I can make sure that we have a build.xml file for each
of the examples.
> 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.
