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

Bug 77900

Summary:	Plugin with missing dependency is silently ignored
Product:	[Eclipse Project] Platform	Reporter:	Michael Valenta <Michael.Valenta>
Component:	Runtime	Assignee:	platform-runtime-inbox <platform-runtime-inbox>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	major
Priority:	P3
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Michael Valenta

2004-11-04 16:17:28 EST

I had created a plugin with a dependency on a project. The project actually 
didn't provide anything useful and was deleted but the dependency was not 
removed. The next time I tried to use the plugin, it was not available. There 
was never an error printed as to why the plugin was not loaded. I actually 
don't care who generates the error (Runtime or PDE) but it makes it very 
difficult to figure out what is wrong if failures are silent. I had the 
project configured to be a bundle and the only indication I got about what the 
cause of the problem was when I tried to do a PDE build. The build wrote the 
error to the log.

Comment 1 Rafael Chaves

2004-11-04 16:27:22 EST

Non-resolved bundles are only logged when -debug is specified. Maybe we should
take -dev as an indication as well (or instead)?

*** This bug has been marked as a duplicate of 75648 ***

Comment 2 Jeff McAffer

2004-11-04 16:42:17 EST

sounds like a good idea (-dev that is).  Any downsides?

Comment 3 Rafael Chaves

2004-11-04 16:47:45 EST

Developers would not have a choice whether they want unresolved bundles to be
logged or not (unless we add another property for disabling it). Anyway, I don't
believe people would be annoyed for unresolved bundles being logged. This is how
it worked in the past (2.x). Maybe we report unresolved bundles with -dev, and
report details on why the bundle was not resolved depending on another key?