[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] updating platform plugins

Hi P2ers,

ECF is looking to simplify it's build for the Galileo release train. Currently, our build is getting progressively more complex, at least partially because we must create and build ECF features that *exclude* the 11 bundles that ECF contributes to the platform (i.e. to support p2 filetransfer).

What we would like to do is to be able to include updates of these 11 bundles in our own major and minor releases (which we cannot do now, because p2 cannot/will not install platform bundle updates...other than by patch features, and patch features are not ideal/easy for us to use in our own build (i.e. see John A's comment below).

p2 had planned to require ECF bundles rather than include them in the platform...there's a bug number for that, but I can't remember what it is ATM (help?). If that was done, would it allow us to update ECF filetransfer bundles in our own releases? Or would that still be an issue?

If technical work on p2 is necessary to accomplish this I'll volunteer for it. The gyrations we have to go through are getting pretty burdensome for us, as we have/schedule our own releases, have multiple release streams, etc...which is why I would like to address this somehow for Galileo.



John Arthorne wrote:

Scott, some answers below. We can discuss on #eclipse-dev if it's still unclear. We'll likely need to wait until Pascal and DJ return in late August before changing how we consume ECF in the platform.

Scott Lewis wrote on 08/07/2008 11:58:09 AM:

> 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?

Patch feature export is supported in 3.4.0 - it was always supported. No hand-crafting of metadata is needed to create patches, but writing a patch feature has always been a somewhat painful and slow process. What we didn't do in 3.4 is support creating patches on the fly when a newer version is dropped into the platform. We're not sure if this will happen in 3.5 either, as we are leaning towards having PDE tooling to greatly simply creation and deployment of patches into the currently running system (see recent comments in bug 222945).

> The build changes for requiring ECF (rather than including it in
> platform) have not yet been made (can't remember bug # on that)...also
> correct?


> Note ECF will soon (after Equinox completes its move probably) be moving
> to the runtime project...so this will affect builds, etc.

No problem, the move should be easy to accomodate on the build side (just update the map file with the new location).
> Thanks...I've been away, but will soon begin attending p2 weekly
> meetings to follow up on both these things/other things.

Yep, lots of vacations still going on here too. I assume there will be a p2 meeting on Monday but there won't be many of us.


p2-dev mailing list