Community
Participate
Working Groups
In the shared install scenario when we are building the osgi.bundles list property for a user's local config.ini we don't consult the shared config.ini. We have a case where there was a bundle (org.eclipse.equinox.event) on the osgi.bundles list in the shared config.ini. When we are building the list of bundles when constructing the user's osgi.bundles list, we remove it from the list because it has the same start level as the default. Therefore when the user list gets written out, it is missing this extra bundle. We should also consider whether or not the osgi.bundles list should be even written at all in the user's local config.ini file. Another approach would be to use cascading. That is, have a new property (or somehow use the old property) and combine the entries from the shared area and the user's area.
Move all 3.8 bugs to Juno.
Feel free to unschedule
Unscheduling
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. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
