Bug 551851 - ModelAssembler.processFragment(MModelFragments, MModelFragment, String, String, boolean) error message is useless
Summary: ModelAssembler.processFragment(MModelFragments, MModelFragment, String, Strin...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.13   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 562497
  Show dependency tree
 
Reported: 2019-10-07 08:37 EDT by Christoph Laeubrich CLA
Modified: 2020-04-26 13:15 EDT (History)
0 users

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 Christoph Laeubrich CLA 2019-10-07 08:37:03 EDT 
org.eclipse.e4.ui.internal.workbench.ModelAssembler.processFragment(MModelFragments, MModelFragment, String, String, boolean) emits an error like this:

"Fragment from <x> of <Y> could not be validated and was not merged <Z>"

But does not include the actual error. So for any non trivial fragment.e4xmi the message is completely useless to the user as he has no idea whats wrong.

The use needs all details from the DiagnosticResult to get an idea whats going on.
Comment 1 Christoph Laeubrich CLA 2019-10-07 08:42:12 EDT 
Current Workaround is to attach a debugger and then extract the necessary information manually.