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

Bug 335712

Summary:	org.eclipse.xtext.ui.shared.internal.Activator stop could be robust against start failures
Product:	[Modeling] TMF	Reporter:	Tim Moore <tmm-bugs.eclipse>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	Flags:	sven.efftinge: kepler+
Version:	1.0.0
Target Milestone:	M4
Hardware:	PC
OS:	All
Whiteboard:

Description Tim Moore

2011-01-28 12:38:41 EST

A bug in our code caused a Guice provision error in org.eclipse.xtext.ui.shared.internal.Activator#start(...). The result was that the resourceChangeListener field wasn't initialized. On bundle stop() this causes an AssertionFailedException to be thrown from ResourceChangeListenerList.

Now, given the large number of errors that were logged due to the injection failure this does seem slightly trivial, but it would be easy to guard against the exception on stop - and every little helps, right? :)

Comment 1 Sven Efftinge

2012-11-20 12:16:44 EST

pushed to masetr

Comment 2 Eclipse Webmaster

2017-10-31 11:31:17 EDT

Requested via bug 522520.

-M.