[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Provisioning work area
- From: "Alex Blewitt" <alex.blewitt@xxxxxxxxx>
- Date: Mon, 19 Feb 2007 21:15:48 +0000
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r3mn0YVSBPl9vF4bzMAM3G+c0d0XvEmLxhwuQbsNuobznT4JhfG6bbA2uWRkYskGtji/3YgHMN8lQe/DGotovvOlfBzIfhLprjS/oENEngdoz+50A1djdPf1BLJso0z9n6Guo70tV9RxDC+AkEweNOus7YYQfC0KWbQEVEGqq50=
I'd love to be involved with this. I've complained about the update
manager for so long that it would be foolish for me not to help out
with this effort :-)
might be of interest for collecting ideas, but I think that a
lower-level approach to provisioning updates for bundles is a good
NB are we going to separate out 'updating bundles' vs 'updating
features'? Although Eclipse primarily uses the latter, having support
for the former would be useful both for Eclipse and also for other
OSGi frameworks; and then the latter could be built on the former.
I'd also gladly contribute code for it too ...
On 19/02/07, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx> wrote:
In an effort to act on the Eclipse Project's 3.3 provisioning plan item, the
creation of a provisioning work area in the Equinox Incubator is being
proposed. A description of the work and scope is available at
Please cast your votes and direct any questions to the
equinox-dev@xxxxxxxxxxx mailing list.
equinox-dev mailing list