You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2015/01/16 11:37:34 UTC

[jira] [Resolved] (SLING-4320) Make JUnit Core depend on JUnit and Hamcrest with Compile scope

     [ https://issues.apache.org/jira/browse/SLING-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved SLING-4320.
------------------------------------
    Resolution: Fixed
      Assignee: Konrad Windszus

> Make JUnit Core depend on JUnit and Hamcrest with Compile scope
> ---------------------------------------------------------------
>
>                 Key: SLING-4320
>                 URL: https://issues.apache.org/jira/browse/SLING-4320
>             Project: Sling
>          Issue Type: Improvement
>          Components: Testing
>    Affects Versions: JUnit Core 1.0.10
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>
> Currently in org.apache.sling.junit.core (1.0.10) the dependency to JUnit and Hamcrest has scope {{provided}}. It should rather have the scope {{compile}} to ease writing of Remote Unit Test Bundles (because only dependencies with {{compile}} scope would automatically be included transitively)
> Those bundles should only depend on sling.junit.core and transitively get the dependencies for JUnit and Hamcrest. Otherwise you always need to figure out manually which JUnit version and Hamcrest version is used by sling.junit.core and add those dependencies manually in addition to the sling.junit.core dependency.



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