[infinispan-issues] [JBoss JIRA] (ISPN-8787) org.hamcrest:hamcrest-core should be a test scoped dependency

[Paul Ferraro (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-8787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated ISPN-8787:
-------------------------------
    Description: 
org.hamcrest:hamcrest-core is currently configured in the parent pom as a runtime dependency, even though it is only a mockito dependency and thus should be scoped to tests.

The reason I filed this is because WF detects org.hamcrest:hamcrest-core as an disallowed transient dependency of infinispan-core.

It looks like this is required as a runtime dependency of infinispan-commons-test.  I don't understand why this is setup as a separate module as opposed to generating a test-jar artifact within infinispan-commons.

  was:org.hamcrest:hamcrest-core is currently configured in the parent pom as a runtime dependency, even though it is only a mockito dependency and thus should be scoped to tests.



> org.hamcrest:hamcrest-core should be a test scoped dependency
> -------------------------------------------------------------
>
>                 Key: ISPN-8787
>                 URL: https://issues.jboss.org/browse/ISPN-8787
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 9.1.5.Final, 9.2.0.CR2
>            Reporter: Paul Ferraro
>
> org.hamcrest:hamcrest-core is currently configured in the parent pom as a runtime dependency, even though it is only a mockito dependency and thus should be scoped to tests.
> The reason I filed this is because WF detects org.hamcrest:hamcrest-core as an disallowed transient dependency of infinispan-core.
> It looks like this is required as a runtime dependency of infinispan-commons-test.  I don't understand why this is setup as a separate module as opposed to generating a test-jar artifact within infinispan-commons.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)