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

Bug 495297

Summary: Context help description of "Organize import" is 'sticky'
Product: [Eclipse Project] JDT Reporter: Andreas Sewe <sewe>
Component: DocAssignee: JDT-Doc-Inbox <jdt-doc-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: trivial    
Priority: P3    
Version: 4.6   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X   
Whiteboard: stalebug

Description Andreas Sewe CLA 2016-06-02 09:51:50 EDT
This is an odd bug. Here are steps to reproduce (using the Neon RC3 Eclipse IDE for Java Developers):

- Open the preferences.
- Go to a page that doesn't have context help configured (e.g., "XML").
- Click the "?" button in the lower left corner to open the help pane.
- Note that this shows "About XML: This dialog allows you to set your workbench preferences", which is the default in case not context help was configured.
- Go to the Java > Code Style > Organize Import preference page (with the help pane still open).
- Note that this shows "About Organize Imports: On this page you can define the sort order of import statements".
- Go the earlier page again.
- This shows now "About XML: On this page you can define the sort order of import statements".

For some reason, the context help description of "Organize Imports" is sticky. Other JDT preference page seem not to be affected. Going to "Java > Code Style" and then to "XML" again still has it showing "About XML: On this page you can define the sort order of import statements".
Comment 1 Eclipse Genie CLA 2019-11-19 04:43:20 EST
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.