Diagnosing is primarily interpreting and understanding the error message.
These are available on the old enRoute site:
https://v2archive.enroute.osgi.org/appnotes/resolving.html
<https://v2archive.enroute.osgi.org/appnotes/resolving.html>
https://v2archive.enroute.osgi.org/appnotes/resolution-notes.html
<https://v2archive.enroute.osgi.org/appnotes/resolution-notes.html>
Kind regards,
Peter Kriens
> On 1 Jul 2019, at 08:27, Alexander Fedorov <alexander.fedo...@arsysop.ru>
> wrote:
>
> Hello,
>
> Recently I tried to use E4 NSL approach (POJO with @Translation annotation)
> inside the Component implementation.
>
> It works fine with plug-in unit tests launched from IDE and it also works
> with IDE UI, but fails with the maven unit-tests.
>
> This particular failure may be related with target platform difference or
> start levels, but my question is more generic:
> what is the proper way to trace OSGi component resolution process?
>
> Regards,
> AF
> _______________________________________________
> platform-dev mailing list
> platform-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
