| How to make the different-version-plugin pickup transparent to the user? [message #52456] |
Wed, 28 May 2003 16:34  |
Eclipse User |
|
|
|
Originally posted by: heather.hotmail.com
Hi,
If a plug-in is provided as a feature to Eclipse with a version number
which changes from build to build, every time when an old build of
Eclipse(customized) with the plug-in is uninstalled and a new build is
installed, when the application is launched for the first time, there will
be a pop-up dialog titled "Configuration Changes". The message reads
"Pending Configuration Changes Check the changes you wish to process
now. Remove changes that should never be processed". The plug-in with the
new version number will be reported (by default all changes are selected
with check marks) as a pending change. Clicking "Finish" on the dialog
will load the plug-in and clicking "Cancel" will leave the plug-in
disabled. (The user can pick up the pending change at a later time.)
My question is: since I would like to keep this kind of plug-in upgrade
transparent to the user, is there a way to prevent this dialog from
appearing and the new version plug-in gets loaded automatically? I've
checked the boot plug-in and couldn't see a way to configure the behaviour
differently.
Anyone has an idea? I realized that if the file named "platform.cfg" under
"workspace/.metadata/.config" gets removed after the installation and
before the application is launched, the goal can be achieved. I'm
wondering if there is a better way or a recommended way to do it.
Thanks very much!
Heather
|
|
|
| Re: How to make the different-version-plugin pickup transparent to the user? [message #53792 is a reply to message #52456] |
Thu, 29 May 2003 08:27  |
| Eclipse User |
|
|
|
Are you really uninstalling as in the removal of the files? And the
installation happens natively (ie not using Update Manager as the
install mechanism)?
If that is the particular case then the simplest answer is never to
deploy the plugin build to build with a different version. Use the same one.
A method some use is to only reversion between "releasing" the
plugin/feature to the world.
If its an internal plugin which you always support by replacing eclipse
(I suspect this is the case, as viewing the trashing of someone's
metadata directory to be a viable option indicates an in-house sort of
control) then you have far more options to play fast and loose with the
guidelines for deployment of the plugins.
As an alternative (I haven't tried this) you could use the -initialize
flag with the current workspace after installing the new plugins. That
may work although it isn't really meant for that.
Peter
Heather wrote:
> Hi,
>
> If a plug-in is provided as a feature to Eclipse with a version number
> which changes from build to build, every time when an old build of
> Eclipse(customized) with the plug-in is uninstalled and a new build is
> installed, when the application is launched for the first time, there will
> be a pop-up dialog titled "Configuration Changes". The message reads
> "Pending Configuration Changes Check the changes you wish to process
> now. Remove changes that should never be processed". The plug-in with the
> new version number will be reported (by default all changes are selected
> with check marks) as a pending change. Clicking "Finish" on the dialog
> will load the plug-in and clicking "Cancel" will leave the plug-in
> disabled. (The user can pick up the pending change at a later time.)
>
> My question is: since I would like to keep this kind of plug-in upgrade
> transparent to the user, is there a way to prevent this dialog from
> appearing and the new version plug-in gets loaded automatically? I've
> checked the boot plug-in and couldn't see a way to configure the behaviour
> differently.
>
> Anyone has an idea? I realized that if the file named "platform.cfg" under
> "workspace/.metadata/.config" gets removed after the installation and
> before the application is launched, the goal can be achieved. I'm
> wondering if there is a better way or a recommended way to do it.
>
> Thanks very much!
>
> Heather
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03889 seconds
Home