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

[Peter Manahan <manahan@xxxxxxxxxx>]

So basically a RCP standalone update
manager. That lives separately from the eclipse installation itself but
can just "administor" your eclipse development installations.
 Taking it to the furthest extent then it may be useful to separate
the update manager UI from eclipse itself and just provide it as an RCP
application which can manage multiple eclipse installs.  Makes a lot
of sense from a product perspective.


Thanks,

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

"Ed Burnette" <Ed.Burnette@xxxxxxx>
Sent by: eclipse-dev-admin@xxxxxxxxxxx

13/02/2004 10:16 AM

Please respond to
eclipse-dev

To	<eclipse-dev@xxxxxxxxxxx>
cc
Subject	RE: [eclipse-dev] Purposal for the packages problem

I think that Eclipse's update manager can fulfil this
requirement -except- if the user doesn't already have Eclipse or they have
an incompatible version. Maybe an RCP bootstrap app that would update-manager
your way into a full install?

> -----Original Message-----
> From: Lawrence Mandel [mailto:lmandel@xxxxxxxxxx] 
> Sent: Friday, February 13, 2004 10:06 AM
> To: eclipse-dev@xxxxxxxxxxx
> Subject: Re: [eclipse-dev] Purposal for the packages problem
> 
> What about creating an Eclipse download manager? In this way the user
can
> select the projects they'd like to install and they'd only get what
they
> select. Take a look at Cygwin's download manager as an example. You
can
> select what components you'd like to install and you only get what
you
> select.
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev