Error running gradlew test on latest master


(ppearcy) #1

FYI, I followed the instructions here:

Running "gradlew test" fails with this error (and some others
similar):
:plugins-transport-memcached:compileTestJava
/home/paul.pearcy/elasticsearch/plugins/transport/memcached/src/test/
java/org/elasticsearch/memcached/test/
AbstractMemcachedActionsTests.java:25: package org.hamcrest does not
exist
import org.hamcrest.Matchers;

So, it appears that a dependency for testing is not being pulled
down?

This isn't causing me any pain, but thought I should let people know.

Thanks,
Paul


(Shay Banon) #2

Right, added a test and forgot to add the dep for it. Fixed in master.

On Thu, Jul 22, 2010 at 6:13 PM, Paul ppearcy@gmail.com wrote:

FYI, I followed the instructions here:

http://wiki.github.com/elasticsearch/elasticsearch/getting-started-with-the-source-code

Running "gradlew test" fails with this error (and some others
similar):
:plugins-transport-memcached:compileTestJava
/home/paul.pearcy/elasticsearch/plugins/transport/memcached/src/test/
java/org/elasticsearch/memcached/test/
AbstractMemcachedActionsTests.java:25: package org.hamcrest does not
exist
import org.hamcrest.Matchers;

So, it appears that a dependency for testing is not being pulled
down?

This isn't causing me any pain, but thought I should let people know.

Thanks,
Paul


(ppearcy) #3

Thanks!

On Jul 22, 12:19 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Right, added a test and forgot to add the dep for it. Fixed in master.

On Thu, Jul 22, 2010 at 6:13 PM, Paul ppea...@gmail.com wrote:

FYI, I followed the instructions here:

http://wiki.github.com/elasticsearch/elasticsearch/getting-started-wi...

Running "gradlew test" fails with this error (and some others
similar):
:plugins-transport-memcached:compileTestJava
/home/paul.pearcy/elasticsearch/plugins/transport/memcached/src/test/
java/org/elasticsearch/memcached/test/
AbstractMemcachedActionsTests.java:25: package org.hamcrest does not
exist
import org.hamcrest.Matchers;

So, it appears that a dependency for testing is not being pulled
down?

This isn't causing me any pain, but thought I should let people know.

Thanks,
Paul


(system) #4