Not including snappy-java was intentional. Users who are running on systems
that support snappy-java can add the <dependency> to their <plugin> by
adding it in always they have no way to remove snappy from the classpath
and hence cannot start C*

Not including snappy-java just gives a warning but C* functions as normal,
and a test instance should not be being fed such a quantity of data that
snappy-java is required, given that it should be a throw away DB anyway


On 11 June 2013 11:39, <[email protected]> wrote:

> **
>  Revision 18397 <http://fisheye.codehaus.org/changelog/mojo/?cs=18397>
> Author olamy Date 2013-06-11 05:39:57 -0500 (Tue, 11 Jun 2013) Log Message
>
> [MCASSANDRA-26] Issue starting cassandra " java.lang.UnsatisfiedLinkError: no 
> snappyjava in java.library.path "
> force last snappy version which fix that (at least locally for me :-) )
>
> Modified Paths
>
>    - 
> trunk/mojo/cassandra-maven-plugin/pom.xml<#13f32d4fb9d8d381_trunkmojocassandramavenpluginpomxml>
>
>  Diff
> Modified: trunk/mojo/cassandra-maven-plugin/pom.xml (18396 => 18397)
>
> --- trunk/mojo/cassandra-maven-plugin/pom.xml 2013-06-11 10:20:02 UTC (rev 
> 18396)
> +++ trunk/mojo/cassandra-maven-plugin/pom.xml 2013-06-11 10:39:57 UTC (rev 
> 18397)@@ -114,6 +114,11 @@         </exclusion>       </exclusions>     
> </dependency>+    <dependency>
> +      <groupId>org.xerial.snappy</groupId>
> +      <artifactId>snappy-java</artifactId>
> +      <version>1.0.5</version>
> +    </dependency>     <!-- Cassandra have not been tracking their transitive 
> dependencies correctly -->     <dependency>       
> <artifactId>netty</artifactId>
>
>   ------------------------------
>
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>

Reply via email to