Community
Participate
Working Groups
Currently there is some API related to SaveParticipants which take a Plugin object as a parameter. We should look into deprecating this and creating equivalent API which accepts a Bundle.
Lowering the priority to better match reality.
*** Bug 292712 has been marked as a duplicate of this bug. ***
Raising priority, as noted in duplicate bug the API can't be used without using the Plugin class which is mostly obsolete and replaced by Bundle. We shouldn't be forcing people into using obsolete classes.
Created attachment 150911 [details] Proposal v01
The API approach using a string looks good (String will never be deprecated ;). There are a few more places in SaveManager that reference the saveParticipants field that will also need fixing up.
(In reply to comment #5) > There are a few more places in SaveManager that reference the saveParticipants > field that will also need fixing up. Right. I marked the latest patch as obsolete, when the resource tests started to glow red. I'll attach the fixed patch in a moment.
Created attachment 150945 [details] Proposal v02
Proposal v02 released to HEAD.
The fix in HEAD causes API errors in my workspace (with a 3.5 baseline).
(In reply to comment #9) > The fix in HEAD causes API errors in my workspace (with a 3.5 baseline). Thanks Markus. My 3.5 baseline is Eclipse SDK 3.5.1 installed via p2Agent. Something wrong happened to the profile and it probably didn't contain all the plug-ins. Thus I couldn't see the API tooling problems. This was a problem with p2Agent not API tooling. I fixed my profile and I am not able to reproduce this issue now. John already fixed the API tooling problems.