Bug 551157 - Improve problem marker "Bundle x.y.z cannot be resolved"
Summary: Improve problem marker "Bundle x.y.z cannot be resolved"
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2019-09-17 06:11 EDT by Lars Vogel CLA
Modified: 2023-08-29 11:33 EDT (History)
1 user (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 Lars Vogel CLA 2019-09-17 06:11:50 EDT 
Currently if A has a dependency which cannot be resolved, we get the problem marker:

"Bundle x.y.z cannot be resolved" 

I have to check Path or click on the message to see which plug-in is affected.

I suggest to change this message to:

"A cannot resolve its x.y.z dependency" 

While A is the placeholder for the affected bundle/plug-in.
Comment 1 Eclipse Genie CLA 2021-09-07 15:37:38 EDT 
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 2 Eclipse Genie CLA 2023-08-29 11:33:59 EDT 
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.