[
https://issues.apache.org/jira/browse/CASSANDRA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988145#action_12988145
]
Eric Evans commented on CASSANDRA-1997:
---------------------------------------
This looks interesting, and useful, but I'm having a hard time reconciling the
changes in CASSANDRA-1805 (for example, the removal of {{contrib/javautils}}
and {{contrib/circuit}} ) with the addition of this to {{tools/}}.
I'd be willing to push-back on CASSANDRA-1805, but I'm more and more inclined
to believe it's the right direction. Projects like cassandra-maven-plugin
target such a specific set of developers/users. I think they can benefit from
the autonomy as much as Cassandra can benefit from not becoming a monolithic
tree of All Things Cassandra.
Stephen, you seemed to indicate elsewhere that your desire to have it in-tree
was to keep it closely associated with the project (i.e. social, not
technical), wouldn't this be an ideal candidate for Apache Extras
(http://code.google.com/a/apache-extras.org/hosting/)?
> Cassandra-Maven-Plugin
> ----------------------
>
> Key: CASSANDRA-1997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1997
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Stephen Connolly
> Attachments: CASSANDRA-1997-v2.patch, CASSANDRA-1997-v3.patch,
> cassandra-maven-plugin.0.7.patch, cassandra-maven-plugin.tar.gz
>
>
> A maven plugin to allow controlling a test instance of cassandra from within
> maven builds
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
