Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 174923 - Rename bundle id action
Summary: Rename bundle id action
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.3 M6   Edit
Assignee: Brian Bauman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-21 03:35 EST by Gunnar Wagenknecht CLA
Modified: 2007-03-15 15:52 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2007-02-21 03:35:12 EST
It would be cool if there would be a rename bundle id operation that would update all references to a bundle if the bundle id is renamed.
Comment 1 Brian Bauman CLA 2007-03-02 16:44:14 EST
The dream is becoming a reality.  With the next build we should have a "rename..." action on the plug-ins view.  It also supports the F2 shortcut for renaming.  This action is only available on workspace bundles.  During the renaming, you can choose to rename require-bundle references in other workspace projects.  You can also rename the project name to match the new bundle-symbolicName.

When I find more time, I will include this action in the Plug-in Dependencies view and some source pages.  
Comment 2 Gunnar Wagenknecht CLA 2007-03-03 06:30:46 EST
AWESOME! With this action we enter the bundle refactoring area. :)
Comment 3 Brian Bauman CLA 2007-03-15 15:52:10 EDT
Included support for renaming in the Manifest Source page (context menu) and Dependencies View (context menu only).  

Getting the F2 shortcut to work on the Dependencies View is going to take some time since the view has multiple pages.  Was able to get it to work, but once a different view/page was selected, the short cut would no longer work.

If you would like to see this rename action go elsewhere in PDE, please reopen this bug.