Bug 381916

Summary: Improve diagnostics for unmatched fragments
Product: [Eclipse Project] Platform Reporter: Brian de Alwis <bsd>
Component: UIAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: malaperle
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug
Bug Depends on:    
Bug Blocks: 562497    

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.