Community
Participate
Working Groups
I20100119-0800 The behavior change mentioned in bug 18500 comment 53 kills our workspace update scenario: > There is a change in behaviour with this fix. When the user imports a plug-in > with a conflict and chooses not to delete the project, previously we would skip > importing that plug-in. After this fix, instead of ignoring, we import the > plug-in and give it a different name. Before, we performed these steps when new plug-ins got added to a build: - Import > Plug-ins and F. - select 'required by existing', as binary - Select All - When asked whether to replace existing, say 'No to All' Now, we can only delete existing projects. If we deselect all in the "do you want to delete?" dialog, we get duplicate plug-ins in the workspace. But replacing existing plug-ins also fails because bug 300354 only imports one version.
This is major regression for the given scenario. A solution would be to add 2 radios to the "Delete Plug-in Projects" dialog: Action for plug-ins that map to unselected projects: o skip o import with a different project name
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.
