Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] ECF remote services support for Eclipse 3.5.x

Just to be clear, p2 will use whatever ECF packages that are installed and will allow them to be upgraded. p2 uses lower bounds on some of the package inclusions, but that's the only restrain that p2 puts on the OSGi runtime with respect to ECF.

Thus, it is possible to both install and to upgrade the ECF bundles today. p2 does not need to rely on a specific ECF feature for that to happen. If you want to upgrade ECF, well then just install a feature of your choice that includes ECF (or upgrade one if it's already present) and p2 will use whatever gets installed.

Example; Buckminster uses ECF. If our core feature is updated, that might imply an upgrade of ECF. As long as all bundles in the targeted runtime are OK with that, with respect to their requirements, there's no conflict.

Thomas Hallgren

On 02/15/2010 11:07 AM, Markus Alexander Kuppe wrote:
On 02/15/2010 09:40 AM, Wim Jongman wrote:
Are you saying that ecf core is not part of ECF but of P2? If so, then
shouldn't p2 be dependend on the ecf core feauture so that it can be
installed an upgraded separately from p2? This instead of including it?
But if it is installed separately, will P2 still work after upgrading
ECF core?
+1 the root cause for this dilemma is the inclusion of ECF in p2. Are we
going to make sure that with Helios, Equinox (p2) is going to reference
ECF's platform feature? Otherwise we will face the same problem again
after Helios.

Trying to understand this. Will there be à conference today?
According to Google Calendar we have a con call scheduled for today
17:00 CET.

ecf-dev mailing list

Back to the top