[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Site objects
|
A few more words on this .....
The example referenced by Christophe is currently not functional. It was
written to treat a regular Eclipse build .zip as an update site, but since
then the build .zip format has changed and the example has not kept pace.
So, although you can't actually execute it, you can look at the code to see
how this was done.
The way this mechanism works is roughly as follows:
* the udpate site declares in its site.xml that it is a site of a specific
type (on the <site type=""> tag)
* eclipse detects this, looks up the declared type in the
org.eclipse.update.core.siteTypes extension point (registers the site
factory)
* if the corresponding factory is found, eclipse calls it to create the
correct site object, and then interacts with it (instead of its default
site object)
* the site object separates the content handling into a content provider
object. So you should be able to reuse the base site implementation we
provide, and combine it with your own content provider (your factory would
"put" the base site and your content provider together).
* the content provider then decides what it exposes from the site ... eg.
can check what is locally installed and filter the site content accordingly
A couple of other comments that relate to controlling what a user can get
from a site (but are not related to having own site implementation)
* features can specify <requires> <import> prereqs on plugins that need to
be installed before the feature can be installed (the import matching rules
are same as in plugin.xml). A feature update can be packaged specifying a
prereq on the feature plugin version it is updating, for example, make sure
1.1.* is not applied unless you have 1.1.0 or service to it (<import plugin
="base.feature.plugin" version="1.0.0" match="equivalent"/>)
* when setting up the site for updates, the complete set of feature .jar's
is needed. However, if you use the prereq as above, you could decide omit
the plugin .jars that have not changed (because with the prereq
specification satisfied you can expect these to be already installed). This
way the updates could generally not be used as a full base (unless you
have managed to change all the base plugins, in which case it is likely
time to reversion and establish a new base).
Hope this helps .....
Christophe
Elek/Toronto/IBM@IBMCA To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@e Subject: Re: [platform-update-dev] Site objects
clipse.org
05/29/2002 07:15 AM
Please respond to
platform-update-dev
Tim,
ISite, ISiteContentProvider and ISiteFactory
Extension point: org.eclipse.update.core.siteTypes
and Example: org.eclipse.update.examples.buildzip
Let us know
Christophe Elek
Eclipse Project: <http://eclipse.org>
IBM canada
Tuesday, May 28, 2002 8:06 PM
To: platform-update-dev@xxxxxxxxxxx
cc:
From: Tim_Koss@xxxxxxx
Subject: [platform-update-dev] Site objects
The latest Eclipse Platform Installation and Update doc talks about a site
object for controlling access. Where can we find more info about this?
Tim
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
