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

Bug 328052

Summary: [Help] Refactoring Project Name Breaks Help Links
Product: [Eclipse Project] Platform Reporter: Ole Ersoy <ole.ersoy>
Component: User AssistanceAssignee: platform-ua-inbox <platform-ua-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: cgold, darin.eclipse, ole.ersoy
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Ole Ersoy CLA 2010-10-18 12:36:25 EDT 
Build Identifier: M20090917-0800

I have a project name (And plugin id):
com.mycompany.useless.piece.of.guide

I refactor the name using eclipse refactoring support, so it's now called com.mycompany.guide.

This changes both the name in the workspace and the plugin id in plugin.xml,but leaves the files system directory name the same, so that if I look at the workspace using ls, the directory holding the project "com.mycompany.guide", is still named "com.mycompany.useless.piece.of.guide".

The guide still loads fine in the eclipse help center, but links to pages in the guide from other help plugins are broken.  

I fixed this by changing the underlying file system name of the project to match the plugin ID.





Reproducible: Always

Steps to Reproduce:
See details.
Comment 1 Chris Goldthorpe CLA 2010-10-19 12:41:57 EDT 
The help system is not listening for refactoring events and I am not surprised that the page links are not updated.

Darin, does this kind of refactoring bug typically get assigned to the component that handles the artifact affected by refactoring ( in this case the help system ) or to the PDE?
Comment 2 Lars Vogel CLA 2019-11-14 02:16: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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.