Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 362127

Summary:	API Use Report (Producer) incorrectly reporting "guilty" Referencing Bundles
Product:	[Eclipse Project] PDE	Reporter:	Tim Renouf <tim.renouf>
Component:	API Tools	Assignee:	PDE API Tools Inbox <pde-apitools-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	4.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Tim Renouf

2011-10-26 15:41:50 EDT

Build Identifier: 20110615-0604

We run the API Use Report (both Consumer and Producer) against our latest build each night and noticed a case where we weren't getting symmetry. In the Producer report we had a bundle with a "guilty" (borrowing a Chris Aniszczyk term here) referencing bundle (i.e. it was colored pink) but in the Consumer report the referencing bundle appeared fine.

Looking further we judged the referencing bundle was fine. Although I couldn't setup a development environment to confirm (not through lack of trying) I think in the UseReportConverter (line 1190), where the background color is set, we call getRowColour(counts) when we mean getRowColour(type.counts) otherwise we just use the same color that was set on the last line of the References table above.

Reproducible: Always

Steps to Reproduce:
1. Create a producer report with a guilty last row in the References table but a fine first row in the Referencing Bundles table.
2. Check the color of the Referencing Bundles table. The first row (and subsequent others) will have pink backgrounds when they should be white.

Comment 1 Tim Renouf

2011-10-26 15:43:18 EDT

I should probably add that we run the reports via the Ant tasks (not that I think this would make much of a difference).

Comment 2 Eclipse Genie

2019-01-10 17:09:56 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.

If you have further information on the current state of the bug, please add it. 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.

Comment 3 Lars Vogel

2019-09-02 14:57:52 EDT

This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.