Bug 247242 - The build.properties' additional.bundles key should participate in rename refactoring
Summary: The build.properties' additional.bundles key should participate in rename ref...
Status: CLOSED DUPLICATE of bug 261756
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2008-09-14 21:57 EDT by Simon Archer CLA
Modified: 2012-10-17 15:38 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Archer CLA 2008-09-14 21:57:32 EDT 
When using PDE's Automated Management of Dependencies feature the build.properties file keeps track of dependencies via the additional.bundles property key.

Unfortunately, when you rename a dependent bundle the refactoring is not done to the additional.bundles property's value.  This results in an error marker against the additional.bundles key in build.properties. The solution today is to manually remove the old bundle name and add the new bundle name.

Please make the additional.bundles property value participate in the refactoring for renaming a bundle.
Comment 1 Chris Aniszczyk CLA 2008-09-15 12:37:35 EDT 
The relevant code is:

org.eclipse.pde.internal.ui.refactoring.FindReferenceOperation

The problem here I can see is tracking down dependants using the secondary classpath...
Comment 2 Curtis Windatt CLA 2012-10-17 15:38:39 EDT 

*** This bug has been marked as a duplicate of bug 261756 ***