[platform-dev] How to trace osgi component resolving?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[platform-dev] How to trace osgi component resolving?

From: Alexander Fedorov <alexander.fedorov@xxxxxxxxxx>
Date: Mon, 1 Jul 2019 09:27:51 +0300
Delivered-to: platform-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/platform-dev>
List-help: <mailto:platform-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/platform-dev>, <mailto:platform-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/platform-dev>, <mailto:platform-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2

Hello,

Recently I tried to use E4 NSL approach (POJO with @Translationannotation) inside the Component implementation.

It works fine with plug-in unit tests launched from IDE and it alsoworks with IDE UI, but fails with the maven unit-tests.

This particular failure may be related with target platform differenceor start levels, but my question is more generic:

what is the proper way to trace OSGi component resolution process?

Regards,
AF

Follow-Ups:
- Re: [platform-dev] How to trace osgi component resolving?
  - From: Peter Kriens

Prev by Date: [platform-dev] PMC Approval required for Committer Election for Kit Lo on Eclipse Platform
Next by Date: Re: [platform-dev] How to trace osgi component resolving?
Previous by thread: [platform-dev] PMC Approval required for Committer Election for Kit Lo on Eclipse Platform
Next by thread: Re: [platform-dev] How to trace osgi component resolving?
Index(es):
- Date
- Thread

Back to the top