This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 411051 - ModelAssembler fails silently if fragment cannot be applied and does not print name of offending bundle
Summary: ModelAssembler fails silently if fragment cannot be applied and does not prin...
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.3   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.3.1   Edit
Assignee: Paul Webster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 403331
Blocks:
  Show dependency tree
 
Reported: 2013-06-18 14:11 EDT by Paul Webster CLA
Modified: 2013-08-28 10:08 EDT (History)
7 users (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 Paul Webster CLA 2013-06-18 14:11:39 EDT 
Fix needs to be ported back

+++ This bug was initially created as a clone of Bug #403331 +++

If the ModelAssembler class fails to merge a model fragment with the runtime application model, it fails without an info message on the console. This makes it hard to identify the problem. 

Together with Markus Kuppe and Lars Vogel we created the following attached patch to give a info message.
Comment 1 Paul Webster CLA 2013-08-09 14:59:40 EDT 
https://git.eclipse.org/r/15304

Eric, could you please review this fix?

PW
Comment 3 Paul Elder CLA 2013-08-26 15:43:51 EDT 
Verified in build 4.3.0.M20130821-0800
Comment 4 Paul Elder CLA 2013-08-28 10:08:05 EDT 
Per comment 3, state should be Verified
Comment 5 Paul Elder CLA 2013-08-28 10:08:17 EDT 
Verified per comment 3.