You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2018. It is now read-only.
It would be very helpful if it was possible to reorder resolution results in the editor as the order in which bundles are loaded may be somewhat important.
Typical case involves org.apache.felix.configadmin bundle which is used to configure other bundles. Sure, from functional point of view the final result must not depend on startup order, but it may produce undesired initial output (e.g. some bundle may generate undesired debug messages before it is configured not to do so by config admin). This is unacceptable in production environments with strict requirements on any and all output (e.g. unexpected debug messages may trigger automated alarms, security escalations etc.).
Alternatively resolver may sort run bundles list by some criteria like static weights assigned to known bundles in accordance to their usage (e.g. config admin should go before loggers, for example).
Currently, the only way to achieve this is manual file editing after each resolve operation which is, obviously, cumbersome and error prone.
The text was updated successfully, but these errors were encountered:
It would be very helpful if it was possible to reorder resolution results in the editor as the order in which bundles are loaded may be somewhat important.
Typical case involves org.apache.felix.configadmin bundle which is used to configure other bundles. Sure, from functional point of view the final result must not depend on startup order, but it may produce undesired initial output (e.g. some bundle may generate undesired debug messages before it is configured not to do so by config admin). This is unacceptable in production environments with strict requirements on any and all output (e.g. unexpected debug messages may trigger automated alarms, security escalations etc.).
Alternatively resolver may sort run bundles list by some criteria like static weights assigned to known bundles in accordance to their usage (e.g. config admin should go before loggers, for example).
Currently, the only way to achieve this is manual file editing after each resolve operation which is, obviously, cumbersome and error prone.
The text was updated successfully, but these errors were encountered: