| Horror scenario: Multiple client reinstall [message #447561] |
Tue, 11 April 2006 03:27 |
Eclipse User |
|
|
|
Originally posted by: steffen.foldager.credit-suisse.com
Hi all
I am currently working on automatic updates (see other post from april
10.), and I have now in my attempts managed to "break" a client.
I goofed up somehow and now the application will not start. "MESSAGE
Bundle update@plugins/org.eclipse.ui.views_3.1.1.jar [28] was not
resolved." in the logfile suggests something went wrong with the update,
but the only place else I can find "update@" is in two binary files
lazy.4 and .bundledata.4 in \configuration\org.eclipse.osgi
This is not the problem now, but it got me to think:
If this was an application in production I would have serious problems,
since I would have broken every client that have updated (which I try to
do automatically on startup, remember?) since my buggy version was placed
on the update site.
All the users will have a program that suddenly will not start with no
apparent explanation. I would quickly fix the update site, but the clients
that are broken can not launch, hence they can not be fixed. My company
then needs to send out an emergency email to all users, asking them nicely
to please download and reinstall our application.
For some managers considering RCP versus web application, this could be a
showstopper. No matter how badly you break a web application, you can
always deploy a working version and the world is in order.
Please, somebody tell me I am wrong. Does anyone have real life experience
with this?
Thanks,
Steffen
|
|
|
Powered by
FUDForum. Page generated in 0.06674 seconds
Home