Bug 381916 - Improve diagnostics for unmatched fragments
Summary: Improve diagnostics for unmatched fragments
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 562497
  Show dependency tree
 
Reported: 2012-06-06 16:53 EDT by Brian de Alwis CLA
Modified: 2020-04-26 13:15 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 Brian de Alwis CLA 2012-06-06 16:53:46 EDT 
I just helped a developer figure out why his fragment wasn't being applied, and eventually resorted to stepping through ModelAssembler#processModel() to discover that he had an incorrect identifier.  We should add some diagnostics to help developers detect when a model fragment doesn't match an element.
Comment 1 Eclipse Genie CLA 2020-01-20 15:55:48 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.