lto:cziege...@apache.org]
> > Sent: Friday, August 17, 2018 7:42 AM
> > To: dev@sling.apache.org; Robert Munteanu
> > Subject: Re: ResourceProviderTrackerTest#testReactivation fails
> > after
> > updating to osgi-mock 2
> >
> > I think the test is wrong - the API
ck an overlaying
>>>> of
>>>> resource providers is not possible - and it was never possible
>>>> outside the old osgi-mock context with the broken service reference
>>>> comparable implementation.
>>>>
>>>> the question is: if the
correct, the code is
>>> wrong
>>> and has to be changed to make overlay possible.
>>> on the other side is this code productive for a long time - maybe
>>> the
>>> test assumption is false?
>>>
>>> stefan
>>>
>>>
>>>>
e overlay possible.
> > on the other side is this code productive for a long time - maybe
> > the
> > test assumption is false?
> >
> > stefan
> >
> >
> > > -Original Message-
> > > From: Robert Munteanu [mailto:romb...@a
t; > From: Robert Munteanu [mailto:romb...@apache.org]
> > Sent: Tuesday, August 14, 2018 6:38 PM
> > To: dev@sling.apache.org
> > Subject: ResourceProviderTrackerTest#testReactivation fails after
> > updating
> > to osgi-mock 2
> >
> >
this code productive for a long time - maybe the test
assumption is false?
stefan
>-Original Message-
>From: Robert Munteanu [mailto:romb...@apache.org]
>Sent: Tuesday, August 14, 2018 6:38 PM
>To: dev@sling.apache.org
>Subject: ResourceProviderTrackerTest#testReactiva
Hi,
I am trying to update the resourceresolver module from 1.4.0 to 2.3.10
to fix some failures in configuring components that are needed by the
ResourceResolver.
However, this makes the
ResourceProviderTrackerTest#testReactivation fail, at line 210 [1].
Since I'm not familiar with neither the
