[
https://issues.apache.org/jira/browse/CASSANDRA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987422#action_12987422
]
Stephen Connolly commented on CASSANDRA-1997:
---------------------------------------------
IMHO It does not make sense for any of the goals to invoke cassandra:start
It is perfectly valid to use the nodetool wrapping goals to manage a cassandra
server that is not controlled by the maven plugin,
Also it is perfectly valid to use one maven instance to run the cassandra
server and then from a second terminal or from an IDE the developer invokes the
nodetool or cassandra-cli wrapping goals.
It might make sense for the cassandra:run to invoke cassandra:load, but IMHO it
would need some finessing in order to ensure that repeated calls to
cassandra:run would only invoke load on the first time the cassandra database
is created... I'd rather get the plugin out before tweaking it to add such
finesses
> 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-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.
