Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359577 - context does not properly start up when o.e.m.context.ui is not activate during task activation
Summary: context does not properly start up when o.e.m.context.ui is not activate duri...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 3.7   Edit
Assignee: Steffen Pingel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 364772
  Show dependency tree
 
Reported: 2011-09-30 11:21 EDT by Steffen Pingel CLA
Modified: 2012-02-06 13:08 EST (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 Steffen Pingel CLA 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 CLA 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 CLA 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.