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

Bug 359577

Summary:	context does not properly start up when o.e.m.context.ui is not activate during task activation
Product:	z_Archived	Reporter:	Steffen Pingel <steffen.pingel>
Component:	Mylyn	Assignee:	Steffen Pingel <steffen.pingel>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	shawn.minto
Version:	unspecified
Target Milestone:	3.7
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	364772

Description Steffen Pingel

2011-09-30 11:21:14 EDT

Steps:
1. Remove ContextUiPlugin.getDefault(); statement in ContextTestUtil.triggerContextUiLazyStart()
2. Run mvn integration-test in org.eclipse.mylyn.java.tests

Tests will fail because the context lazy start extension was not executed. I suspect that the reason is activation of the o.e.m.context.ui bundle during pre-activation which causes the initialization code to register the context listener after pre-activation.

This needs to addressed to ensure proper initialization of the context UI (e.g. through an extension point).

Comment 1 Steffen Pingel

2011-09-30 11:35:48 EDT

I have committed a work-around for the Java tests that ensures initialization of Context UI before first task activation but we should fix this properly and add a test.

Comment 2 Steffen Pingel

2012-02-06 13:08:03 EST

This was fixed as part of bug 364772. Activation of o.e.m.context.ui is not explicitly triggered by o.e.m.context.tasks.ui during pre task-activation.