pieter martin created TINKERPOP3-687:
----------------------------------------

             Summary: gremlin-code pom has test scoped dependencies in it
                 Key: TINKERPOP3-687
                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-687
             Project: TinkerPop 3
          Issue Type: Bug
          Components: structure
    Affects Versions: 3.0.0.GA
            Reporter: pieter martin


gremlin-core's pom.xml has the following dependencies

{code}
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>${junit.version}</version>
        </dependency>
        <dependency>
            <groupId>org.mockito</groupId>
            <artifactId>mockito-all</artifactId>
            <version>1.9.5</version>
        </dependency>
        <dependency>
            <groupId>org.hamcrest</groupId>
            <artifactId>hamcrest-all</artifactId>
            <version>1.3</version>
        </dependency>
{code}

These should be scoped test
{code}<scope>test</scope>{code}

I noticed this trying to debug strange MethodNotFound exception when running

{code}Assert.assertThat(traversal.next().id(), 
CoreMatchers.anyOf(CoreMatchers.is(id2), CoreMatchers.is(id3)));
{code}

This happens when there are duplicate hamcrest classes on the class path.

Changing gremlin-core's pom to include test scope for test stuff resolved my 
issue.

{code}org.apache.tinkerpop.gremlin.process.traversal.strategy.decoration.PartitionStrategy{code}

contains some test import statements. Its the only class where test 
dependencies leaked into.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to