You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Kaminski (JIRA)" <ji...@apache.org> on 2011/01/19 16:54:44 UTC
[jira] Commented: (CASSANDRA-1997) Cassandra-Maven-Plugin
[ https://issues.apache.org/jira/browse/CASSANDRA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983764#action_12983764 ]
Chris Kaminski commented on CASSANDRA-1997:
-------------------------------------------
For the record, line 76 of src/it/smoke/pom.xml should be
<version>2.4.2</version>
and not
<version>2.2</version>
This plugin has ERASED all the issues I've been having trying to coax maven into starting cassandra for my integration tests. I had run into a dead-end with antrun, and my integration tests build on each other, so I couldn't use the EmbeddedCassandraService in Hector like I do my unit tests. I toyed around with building test suites in Junit, but this was simply faster and cleaner all around.
> Cassandra-Maven-Plugin
> ----------------------
>
> Key: CASSANDRA-1997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1997
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Stephen Connolly
> Fix For: 0.7.1, 0.8
>
> Attachments: 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.