[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] IServiceListener API break
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Thu, 14 Aug 2014 15:15:15 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
On 8/14/2014 3:03 PM, Alex Blewitt wrote:
Plug-ins that use the Eclipse registry need to be singletons, and ECF uses the registry for its data.
Although this used to be true, as of the work on  it's not required
for the parts of ECF that can be used in non-Eclipse contexts (e.g.
It would be a good idea to enable API baselines, so that you get notified ahead of such breaking changes. You should also add @noimplement to interfaces if they aren’t expected to be implemented by clients, because that will indicate that they shouldn’t implement them (i.e. they use consumer role). The way to avoid these problems is to introduce a new IXxx2 interface, which is ugly but at least works.
Thanks...in general we do enable API baselines. In this case the major
version was changed and @noimplement wasn't appropriate (although as
Alex says noimplement is useful for clients when appropriate).