RE: [eclipse-dev] Purposal for the packages problem

[Peter Manahan <manahan@xxxxxxxxxx>]

eclipse-dev-admin@xxxxxxxxxxx wrote on 13/02/2004
10:53:50 AM:

> 
> 
> > So basically a RCP standalone update manager. 
> > That lives separately from the eclipse installation 
> > itself but can just "administor" your eclipse development
> > installations. 
> 
> Given Pascal's demo Equinox at EclipseCon, the standalone update manager
> could have the appearance of being "standalone" but could
actually be a
> small app which sits on top of the core and loads all of the other
features.
> Using this approach the update manager would be available both prior
to the
> install of the bulk of Eclipse, and also from within Eclipse Workbench
once
> the rest of Eclipse was installed. 

If you take that a little further and have a separate RCP applicaton to
do this work it could provide the ability to discover/update multiple eclipse
based installations on a user's machine. They could have an RCP business
application, eclipse 2.1.2, eclipse 3.0 M6, eclipse 3.0 M7 , WSAD ....
etc.  Basically it would decouple the version/instance of eclipse
running the update manager UI is running on from instance(s) eclipse of
 version you actually want update. It could actually solve many of
the problems that occur when you need update non-plugin/feature portions
of eclipse based applications.

Something to consider anyway :-)



-----------------------------------
Peter Manahan
IBM Rational Tools
Common Install
------------------------------------
manahan@xxxxxxxxxx