Bug 338739

Summary:	Create problem markers for problematic features
Product:	[Technology] CBI	Reporter:	Kenn Hussey <Kenn.Hussey>
Component:	CBI p2 Repository Aggregator	Assignee:	Project Inbox <b3.aggregator-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P1	CC:	miles.daffin, thomas
Version:	unspecified	Keywords:	plan
Target Milestone:	---	Flags:	Kenn.Hussey: indigo+
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	Debug - Missing Dependencies
Bug Depends on:
Bug Blocks:	338741

Description Kenn Hussey

2011-03-02 16:42:56 EST

Please enhance the b3 aggregator editor to create problem markers for features which have missing dependencies and/or which introduce conflicting IUs. Such markers should show up in the Problems View and allow navigation to the problematic element(s) in the editor.

This would involve:

- finding out how to access the information describing the problems during the aggregation (creation of the plan)

- implementing a way to associate this information with the nodes in the model

- hook the problem markers at appropriate places

Comment 1 Michal Ruzicka

2011-04-14 08:40:16 EDT

Problem markers are now created for *Contributions* rather than for features as features cannot be moved to different aggregates individually.

Comment 2 Thomas Hallgren

2011-04-20 10:36:25 EDT

When testing this, I don't see any indication on the failing node, telling me that the node is somehow broken. The "marker" shows up in the problems view and clicking on it brings focus on the failing contribution, so that part seems to be working.

Compare this with what happens when a repository URL is wrong. I then get a red cross on the root node, on the aggregation, on the contribution, and on the failing repository. Except for the last cross, the behavior should be the same here.

Comment 3 Thomas Hallgren

2011-04-27 11:56:18 EDT

Added image overlays when contribution is broken. Fixed in trunk, rev 1466.

Comment 4 Thomas Hallgren

2011-07-09 03:55:59 EDT

*** Bug 293073 has been marked as a duplicate of this bug. ***

Comment 5 Miles Daffin

2011-07-26 06:48:29 EDT

Given the hierarchical information in the error messages I do not think it necessary to put problem markers below the contribution level. Issue closed IMO.

Comment 6 Thomas Hallgren

2011-07-26 08:42:03 EDT

Comment 7 David Williams

2016-09-16 15:51:47 EDT

[Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI.
Made no changes to assignee's for closed bugs, even though some were old inbox.]