Sorry, that was for sure an oversight. Thanks Stefan for fixing it.
Konrad
> Am 08.09.2016 um 17:38 schrieb Andrei Dulvac <[email protected]>:
>
> Thanks a lot Stefan!
>
> On 08/09/16 17:32, "Stefan Seifert" <[email protected]> wrote:
>
> i'm quite sure this was an oversight - i've changed the scope to "test" in
> rev. 1759850
>
> stefan
>
>> -----Original Message-----
>> From: Andrei Dulvac [mailto:[email protected]]
>> Sent: Thursday, September 8, 2016 4:41 PM
>> To: dev; [email protected]
>> Subject: junit teleporter - is mockito needed with scope compile?
>>
>> Hi Konrad, all,
>>
>> In my upstream project, I've had a real issue when I updated my dependency
>> to the latest teleporter, as mockito is brought in in the latest
>> teleporter, and that one shadows stuff like the hamcrest matchers so I get
>> a weird failure inside junit Assume.
>>
>> As part of SLING-5677, in r1743902, you added mockito with the default
>> maven scope. Can it be just "test"? Is it actually used outside the tests
>> for the teleporter itself?
>>
>> Cheers,
>> - Andrei
>
>
>
