[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] updating platform plugins
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Thu, 07 Aug 2008 05:58:09 -1000
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 18.104.22.168 (Windows/20080708)
For p2 ECF included 6 plugins in the platform. In a previous dialog
(see below) we discussed briefly how the ECF project can/could update
these 6 plugins on a schedule separate from the platform.
I just want to confirm the following...according to bug 222945 ECF
can/could create a feature patch and update the six ECF plugins with
that. The necessary PDE changes (to support feature patch export?) are
soon to be made, but meta-data can/could be crafted by hand to do this
if necessary/desired. Correct?
The build changes for requiring ECF (rather than including it in
platform) have not yet been made (can't remember bug # on that)...also
Note ECF will soon (after Equinox completes its move probably) be moving
to the runtime project...so this will affect builds, etc.
Thanks...I've been away, but will soon begin attending p2 weekly
meetings to follow up on both these things/other things.
Pascal Rapicault wrote:
That said, I believe that ECF's situation is still relatively
exceptional in that it is now split between the platform and its own
feature, and that ECF should not be delivered by patches and that the
platform should just require ECF.
Inactive hide details for John Arthorne---05/01/2008 02:34:45 PM---p2
now supports feature patches, so a feature patch can be uJohn
Arthorne---05/01/2008 02:34:45 PM---p2 now supports feature patches,
so a feature patch can be used to replace a plug-in in the base
platform. However, we didn't g
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
05/01/2008 02:34 PM
Re: [equinox-dev] [prov] handing of patches
p2 now supports feature patches, so a feature patch can be used to
replace a plug-in in the base platform. However, we didn't get to our
desired goal of spoofing up patches automatically if the user dropped
in a new version of the bundle in dropins. Here is the bug report
where you can follow progress on this: