Hi all Karafians,
It turns out that this exception is something that can be thrown in response to
some other problem. In my case, a uses constraint violation:
{root=Uses constraint violation. Unable to resolve resource utils.common
[utils.common/3.1.0.BUILD-201609281517] because it is exposed to package 'rx'
from resources io.reactivex.rxjava [io.reactivex.rxjava/1.1.0] and
io.reactivex.rxjava-reactive-streams
[io.reactivex.rxjava-reactive-streams/1.0.1] via two dependency chains.
I found this by breaking in the ResolverImpl and inspecting faultyResources,
which contained the real error. I do not know why the true cause is hidden.
I’ve created a JIRA at KARAF-4750 - Installing a feature can result in an
ResolutionException which incorrectly reports the underlying issue
<https://issues.apache.org/jira/browse/KARAF-4750>.
Best, Dan.
> On 30 Sep 2016, at 08:51, Daniel McGreal <[email protected]> wrote:
>
> Can I get any assistance with this?
>
> How can I get logs from the wiring process?
> Any clue why org.eclipse.equinox.region.management might not be resolved?
>
> Thanks, Dan.
>
>> On 29 Sep 2016, at 10:20, Daniel McGreal <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Any ideas how I can proceed to debug this? Can I get any logs from the
>> feature resolution process to find out why the Eclipse bundle comes into the
>> frame?
>
