Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365636 - unify notification architecture
Summary: unify notification architecture
Status: CLOSED MOVED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Steffen Pingel CLA
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2011-12-05 12:12 EST by Steffen Pingel CLA
Modified: 2011-12-05 12:12 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2011-12-05 12:12:39 EST
As part of bug 361048 the notifications framework was generalized and moved into Mylyn Commons. There are parts in Mylyn Tasks that still duplicate some of the notification architecture which should be generalized:

* Service message notifications should go through the commons mechanism
* Due date reminders and task list notifications should go through the common mechanism
* All configuration should be handled through the Notifications preferences page
* Notifications should be rendered with a common component
* Actions should be handled through an extensible framework 

Classes that need to be considered are: TaskListNotificationPopup, NotificationPopup, BuildsServiceMessageControl, TaskListServiceMessageControl.
Comment 1 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST
Mylyn has been restructured, and our issue tracking has moved to GitHub [1].

We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub.

[1] https://github.com/orgs/eclipse-mylyn