On 10 Sep 2010, at 12:39, Tristan Tarrant wrote:

On Fri, Sep 10, 2010 at 13:21, Galder Zamarreño <galder@redhat.com> wrote:

What temporary file system storage is this? Is it related to Cassandra itself? Or the fact that you use the FileCacheStore? ${java.io.tmpdir} is fine for the moment, but if the storage is pluggable, it would be good to have an in-memory counter part that can be used in unit testing, ala DummyInMemoryCacheStore.

Yes it's for Cassandra: within the unit tests I start an embedded Cassandra server which needs access to the filesystem.

Have a look at how the FileCacheStore tests set up and tear down temp filesystem space:

http://fisheye.jboss.org/browse/Infinispan/branches/4.2.x/core/src/test/java/org/infinispan/loaders/file/FileCacheStoreTest.java?r=2030#l33

> Also, my code is based on a Cassandra Connection Pool I have developed (and is available at http://github.com/tristantarrant/cassandra-connection-pool).
>
> The connection pool and its dependencies (such as the cassandra 0.6.5 jar) are hosted on my private Maven repository. How should we handle that ? Publish them to JBoss' Nexus ?

What are the guarantees that your private repo will be up and running?

Hopefully, for as long as possible. But the question is, do you trust my word for it ?
I've seen people use github as a Maven repo, but I don't really like that.

Aren't these deployed in a maven repo elsewhere? E.g.,

http://code.google.com/p/cassandra-maven-redist/

If you want to use JBoss' Nexus repo to push Cassandra artefacts, we could probably get you access to this.

Cheers

Manik