[
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
|
So in the scenario where you have a product stack. Where lower level
products have fewer plugins that higher ones. An example being WSAD and
WSAD-IE. If we install WSAD then upgrading it to WSAD-IE but just adding
the new plugins we'd like that dialog NOT to appear because at this point
WSAD isn't on the system anymore only WSAD-IE is and the user has already
made the conscious decision to install via the native installer. Shouldn't
have to say yes twice.
What is the correct way to handle this situation. Do we have to do some
magic like blowing away the .config dir first before we call -initialize?
Thanks,
-----------------------------------
Peter Manahan
WebSphere Tools
Build/Install and
Product Architecture
------------------------------------
manahan@xxxxxxxxxx
Vlad
Klicnik/Toronto/IBM@IBMCA To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@ Subject: Re: [platform-update-dev] Update manager UI on detection of new features
eclipse.org
07/25/2002 09:04 AM
Please respond to
platform-update-dev
The -initialize startup will work only on the very first install, getting
all new features picked up automatically (ie. configured by default without
the user prompt ("optimistic reconciliation")). Once you have an
initialized workspace (ie. Eclipse has beed started once) changes are not
automatically configured ... the user is prompted before the changes are
actually configured ("pessimistic reconciliation").
So, whether -initialize will work for you depends on whether the install
you are doing is the initial one, or some subsequent one (eg. adding WSDD
as an "extension" to some existing base).
Peter
Manahan/Toronto/IBM@IBMCA To:
platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@ Subject: Re:
[platform-update-dev] Update manager UI on detection of new features
eclipse.org
07/24/2002 03:45 PM
Please respond to
platform-update-dev
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
_______________________________________________
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
