[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Update manager UI on detection of new features
|
I think calling "eclipse -initialize -nosplash" would work. It is what we
do for the WSAD installs.
Thanks,
-----------------------------------
Peter Manahan
WebSphere Tools
Build/Install and
Product Architecture
------------------------------------
manahan@xxxxxxxxxx
"Tim Koss"
<Tim_Koss@xxxxxxx> To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@ Subject: [platform-update-dev] Update manager UI on detection of new features
eclipse.org
07/24/2002 03:09 PM
Please respond to
platform-update-dev
In WSDD we have lots of data that comes with our install/updates that uses
install handlers to lay them down on the users system. Most of these are
not a part of the base install and the user simply uses the update manager
to get them. For the ones that are a part of the base install we are going
to lay down the features with our installer. We have implemented the
completeConfigure() method in our install handlers to deal with completing
the install when Eclipse runs.
The problem with all this is that when Eclipse runs the first time, it
throws the update manager in forint of the user asking him about installing
these new features. Is there a way we can call Eclipse in a headless
fashion at the end of our install to complete this configuration so the
user does not get this cryptic dialog?
Tim
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
