Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 293073 - [aggregator] Add problem markers on failed model verification/build
Summary: [aggregator] Add problem markers on failed model verification/build
Status: CLOSED DUPLICATE of bug 338739
Alias: None
Product: CBI
Classification: Technology
Component: CBI p2 Repository Aggregator (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-22 13:03 EDT by Miles Daffin CLA
Modified: 2016-09-16 15:51 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Daffin CLA 2009-10-22 13:03:49 EDT
If errors arise when verifying and building a model then problem markers should be applied to appropriate nodes in the model (like they are when a
previously mapped feature has disappeared from the parent mapped repo, or when 
repo is no longer valid - down/moved/missing). 

For example, I just verified a model and got this error: 

Unable to resolve partial IU. Artifact file for
org.eclipse.buckminster.aggregator.p2.impl.ArtifactKeyImpl@f111badb
(classifier: osgi.bundle, id: de.babe.eclipse.plugins.QuickREx_I18N, version:
1.0.0) did not contain a bundle manifest

In situations like this I would like to be able to quickly find the the problem
in the model. In this case I have mapped a feature that contains this plugin,
so I would like to see an error type problem marker on the feature and on all
parent nodes. This marking of problem nodes will make it easier to handle them:
remove or reconfigure or disable etc. When the verification is run again all
markers will be removed in the standard manner.
Comment 1 Karel Brezina CLA 2009-10-26 11:04:54 EDT
Well, since not all verification problems can be displayed in the current model (e.g. missing feature), I'd propose a different approach.

Verification would open a "Resolution" view with a resolution tree. Unresolved nodes would be displayed using a different color, tooltips would provide more details. Resolution problems would be listed even in a "Problems" view under category "Resolution".
Comment 2 Miles Daffin CLA 2009-10-30 07:04:51 EDT
Gut response: I think adding views will complicate things. We need to keep the Aggregator as simple as possible. 

Question 1: Why can't all verification problems be displayed in the current model? 

Question 2: Would this mean that all markers would be removed from the current model, and only appear in the new Resolution view? (Is 'Resolution' the right word? Would 'Verification' be better/more consistent?)
Comment 3 Thomas Hallgren CLA 2011-07-09 03:55:59 EDT
Closing this as a duplicate since problem markers are now added.

*** This bug has been marked as a duplicate of bug 338739 ***
Comment 4 David Williams CLA 2016-09-16 15:51:57 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.]