[
https://issues.apache.org/jira/browse/SLING-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14280017#comment-14280017
]
Konrad Windszus commented on SLING-4320:
----------------------------------------
Since I am talking about a module which provides remote unit test they must
depend on the same JUnit version as is provided during the execution of these
tests (otherwise the execution may fail).
If you already have regular (client side) unit tests in the same module I agree
that you might run into problems, but still I would think that the remote unit
tests have to use the compile classpath while the client side unit test use the
test classpath.
> 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
>
> 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)
