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.
From: John Arthorne/Ottawa/[EMAIL PROTECTED]
To: Equinox development mailing list <[email protected]>
Date: 05/01/2008 02:34 PM
Subject: 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:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=222945
John
Scott Lewis <[EMAIL PROTECTED]>
Sent by: To
[EMAIL PROTECTED] Equinox development mailing
list
<[email protected]>
04/28/2008 11:48 PM cc
Subject
Please respond to [equinox-dev] [prov] handing
Equinox development mailing list of patches
<[email protected]>
With the recent changes/additions for patch handling, will p2 now allow
the update/patch of platform plugins (including, for example, ECF6)?
Reason I ask...ECF currently has to create separate builds (and ask
people to use different update sites) for ECF-on-eclipse 3.3-3.4M5, and
ECF-on-eclipse 3.4M6+ because of the p2 'patch problem'. Just want to
know if this is still an issue (my expectation is yes this is still an
issue, but would like to be sure).
Thanks,
Scott
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
