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

Bug 326895

Summary:	Extend commons notification framework to support builds notifications
Product:	z_Archived	Reporter:	Torkild Resheim <torkildr>
Component:	Mylyn	Assignee:	Mylyn Inbox <mylyn-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Torkild Resheim

2010-10-04 04:28:32 EDT

The commons notification framework should be extended to support builds notifications instead of having a semi-duplicated implementation.
See bug 325079 comment #16.

Comment 1 Torkild Resheim

2010-10-04 04:55:23 EDT

In order to make the BuildsView a notification sink I will have to change this extension point a bit. Sinks should implement a new INotificationSink instead extending NotificationSink.

Comment 2 Torkild Resheim

2010-10-04 04:56:38 EDT

(In reply to comment #1)
> In order to make the BuildsView a notification sink I will have to change this
> extension point a bit. Sinks should implement a new INotificationSink instead
> extending NotificationSink.
As a side note. I also think it makes much more sense as NotificationSink does not provide any features.

Comment 3 Torkild Resheim

2010-10-04 08:27:17 EDT

Well, it appears that we don't really have to do any changes.

Comment 4 Steffen Pingel

2010-10-04 17:49:22 EDT

The reason for using an abstract class is that it allows us to add methods in the future without having to create INoitifcationSink2 ..3 etc.