Bug 184084 - [Refactoring] Renaming an .exsd file should cause plugin.xml to be updated
Summary: [Refactoring] Renaming an .exsd file should cause plugin.xml to be updated
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: bugday
Depends on:
Blocks:
 
Reported: 2007-04-25 14:33 EDT by Simon Archer CLA
Modified: 2019-09-09 02:32 EDT (History)
1 user (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 2007-04-25 14:33:46 EDT 
When I rename an .exsd file (that holds my extension point XSD), I would expect the reference to the file to be changed in the <extension-point>'s "schema" attribute in plugin.xml, but it is not.
Comment 1 Wassim Melhem CLA 2007-04-26 11:57:08 EDT 
you give people an inch...

Brian, this is not for 3.3
Comment 2 Simon Archer CLA 2007-04-26 13:33:19 EDT 
I agree that this is minor and not for 3.3.
Comment 3 Chris Aniszczyk CLA 2008-03-08 17:01:18 EST 
tagging bugday
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:30:38 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 5 Eclipse Webmaster CLA 2019-09-06 15:38:32 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 6 Julian Honnen CLA 2019-09-09 02:32:37 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.