Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 225121 - Problems in plugin.xml not updated when schema changes
Summary: Problems in plugin.xml not updated when schema changes
Status: CLOSED WONTFIX
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: stalebug
Keywords:
: 235861 (view as bug list)
Depends on:
Blocks: 321781
  Show dependency tree
 
Reported: 2008-04-01 11:14 EDT by Dani Megert CLA
Modified: 2019-09-09 02:30 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 Dani Megert CLA 2008-04-01 11:14:06 EDT 
3.4 M6

When changing a schema in plug-in A I expect that problems in plug-in B's plugin.xml file are updated (assuming auto-build is on). This is not the case.

Test Case:
1. make sure auto-build is on
2. open a schema (e.g. markerAnnotationSpecification.exsd in o.e.ui.editors)
3. go to 
<meta.attribute kind="identifier" basedOn="org.eclipse.ui.editors.annotationTypes/type/@name"/>
4. change @name to @bug
5. save
6. go to another project's plugin.xml (e.g. o.e.search/plugin.xml)
==> no warnings are added - all looks good

I either have to change and save that plugin.xml or clean the project. To get all my plugin.xml files updated I have to do a full build!
Comment 1 Chris Aniszczyk CLA 2008-06-05 12:14:37 EDT 
*** Bug 235861 has been marked as a duplicate of this bug. ***
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:36:04 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 3 Julian Honnen CLA 2019-09-09 02:30:20 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.