Jonathan Ellis jbel...@gmail.com writes:
there's some support for this in 0.7 (see
http://issues.apache.org/jira/browse/CASSANDRA-1018) but fundamentally
it's not really designed to be started and stopped multiple times
within the same process.
I am currently struggling with some of the same
separate jvm is the only mechanism to 'shutdown' in a test scenario
right nowand its unlikely to change in the short term so designing
around forking is your best bet
cheers,
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Tue, Jul 20, 2010 at 05:47, Bjorn Borud bbo...@gmail.com
Ran, I do know to run jest in own thread with maven surefire plugin, but
don't sure how can I do this with own JVM for each test. How are you doing
this? Thanks.
On Fri, Jul 9, 2010 at 10:33 PM, Ran Tavory ran...@gmail.com wrote:
The workaround I do is fork always. Each test pulls up its own
look at my pom. it has forkModealways/
http://github.com/rantav/hector/blob/master/pom.xml#L95
On Wed, Jul 14, 2010 at 3:02 PM, Andriy Kopachevsky
kopachev...@gmail.comwrote:
Ran, I do know to run jest in own thread with maven surefire plugin, but
don't sure how can I do this with own JVM for
there's some support for this in 0.7 (see
http://issues.apache.org/jira/browse/CASSANDRA-1018) but fundamentally
it's not really designed to be started and stopped multiple times
within the same process.
On Thu, Jul 8, 2010 at 3:44 AM, Andriy Kopachevsky
kopachev...@gmail.com wrote:
Hi, we are
The workaround I do is fork always. Each test pulls up its own jvm.
On Jul 9, 2010 9:51 PM, Jonathan Ellis jbel...@gmail.com wrote:
there's some support for this in 0.7 (see
http://issues.apache.org/jira/browse/CASSANDRA-1018) but fundamentally
it's not really designed to be started and stopped
Hi, we are trying to set up intergation testing for Cassanrda, so we need to
run and stop it as embeded service. Don't have any problem to start
cassandra:
import
org.apache.cassandra.contrib.utils.service.CassandraServiceDataCleaner;
class SomeTestClass {
@Before
public void setup()
