Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331103

Summary: Plug-in Manifest Editor clears Selection when History Link-with-Editor is on
Product: [Eclipse Project] PDE Reporter: Martin Oberhuber <mober.at+eclipse>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Martin Oberhuber CLA 2010-11-25 04:51:49 EST
Build ID: I20101116-0800

Steps to Reproduce:
1. In a Plugin project, dbl click MANIFEST.MF to load into the editor.
2. Right-click > Team > Show History on the file, enable "Link with Editor".
3. In package explorer, enable "Link with Editor".
4. In package explorer, click on plugin.xml 

--> Selection is cleared again, and MANIFEST.MF is selected instead.

This is extremely annoying when doing a complex multi-select holding the Ctrl key, eg in order to commit multiple files. As soon as the MANIFEST.MF is selected, the entire multi-select is gone again.

Workaround: ensure that the History view is not shown. Or, disable link-with-editor.

It looks like the problem is an odd interaction between the multipage editor changing the page it displays, the history view's link-with-editor feature and the package explorer's link-with-editor feature.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:05:59 EDT
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.
Comment 2 Julian Honnen CLA 2019-09-09 02:26:48 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.