[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Orphan plugins
|
Susan, you are correct about the options. Update manager tolerates orphaned
plug-ins in that it passes them through to Eclipse run-time, but we are not
taking them into account when checking dependencies. I would invite
developers from products to comment on whether they would object to Eclipse
checking 'orphaned' plug-is for dependencies.
Our only concern is legal rather than technical. Orphaned plug-ins are
typically unzipped i.e. not installed professionally (although native
installers also move files outside Update Manager, they typically install
features, not only plug-ins, so we have no problem with that).
Regards,
Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745 T/L 969-2745
Fax. 905 413-4854
"Foster, Susan B"
<susan.b.foster@xxxxxxxxx> To: <platform-update-dev@xxxxxxxxxxx>
Sent by: cc:
platform-update-dev-admin@ Subject: [platform-update-dev] Orphan plugins
eclipse.org
06/03/2003 05:44 PM
Please respond to
platform-update-dev
I posted the following to the newsgroup:
> I am trying to add a plugin using the Update/Install Manager. This
plugin
> requires some of the cdt plugins, among others. When I create a
Feature
> the Required Features/ Plugins are calculated, and the Feature exports
ok.
> I then have created an Update Site Project. But when I try and
install
> it using the Update/Install Manager I get an error
Dorian replied:
>This is a known limitation in the UpdateManager. When required plug-ins
>validation is performed,
>only plug-ins owned by currently configured features are considered.
>Orphaned plug-ins (those that appear in the 'plugins' directory but are
not
>owned by any feature) are ignored.
>Feel free to discuss this on the platform update developer's mailing
list >if
>the current install behavior is undesireable.
The current install behavior mandates that to be updatable by the Update
Manager, a plugin must not be dependant on any orphan plugin - and at
this point that would mean that the cdt would not be updateable.
Is there some way to work around this limitation for the present? It
appears that my two options are to create a Feature that owns the cdt
plugins, or to try to removed the dependence on the cdt plugings.
Susan
email: susan.b.foster@xxxxxxxxx
phone: 480-552-0927
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
