Community
Participate
Working Groups
We resolve our state a number of times in SimpleConfiguratorManipulator and this call is very expensive. It looks like for the typical case we can optimize what we're resolving when saving to a smaller set of bundles (just those required for resolving the bundles on osgi.bundles)and when updating the manipulator's set of bundles possibly avoiding resolving altogerther.
Given all of our efforts around reading and writing fwk admin only once. I will remove this from 3.5. We have more important things to address.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
I assume this issue is stale and/or has already been addressed.
