Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] dependency on Runtime

Hi Jeff,

OK, we'll start moving things over...with some occasional help from Equinox team.  Use bug to track (Chris A filed):


Jeff McAffer wrote:

For one the Equinox provisioning work is looking at ECF.  More to the point however is that the runtime bundle has been largely gutted.  The registry is out, content types, prefs, ...  Tom moved the app model out, ...  most of the helper classes are in Common.  So basically it is things like Platform and Plugin that are left.  There are new best practices for most of these uses.  Note that we have not moved particularly quickly to get people off runtime because some of the new best practices are not all that friendly.  For example, it is way more fun to say Platform.getExtensionRegistry() than to do some service lookups etc.  We have to develop equivalently simpler (and hopefully more decoupled) alternatives before pushing for general adoption.  ECF however is more infrastructure and can benefit from the increased potential for the relatively modest pain.

Like I said, we are happy to help having done this several times in the past.


Scott Lewis <slewis@xxxxxxxxxxxxx>
Sent by: ecf-dev-bounces@xxxxxxxxxxx

03/04/2007 02:51 PM

Please respond to
"Eclipse Communication Framework \(ECF\) developer mailing list."        <ecf-dev@xxxxxxxxxxx>

"Eclipse Communication Framework (ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>

Re: [ecf-dev] dependency on Runtime

Hi Jeff,

Jeff McAffer wrote:

I was looking through some of the ECF bundles and noticed that many have a direct dependency on org.eclipse.core.runtime.  ECF is generally useful and some scenarios for its use do not include the Runtime bundle and all the things that it brings with it.  For the most part the dependencies fall into the following categories

- use of Platform for the convenience methods (getExtensionRegistry, ...)

- use of Plugin to get debugging and logging info

- access to classes that are now in org.eclipse.equinox.common

Note that things like the Plugin class are very "out of fashion" and should be avoided.

For the most part these all have simple alternatives that do not involve the Runtime bundle proper.  Where things are not so straightforward the Equinox team is very interested in making them simple :-)  I'd be happy to work with the ECF community to remove the dependencies on Runtime so that we can use ECF in some additional scenarios.

Sure, we can make such changes.  What additional scenarios were you thinking of that would not involve runtime?


ecf-dev mailing list

_______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx

Back to the top