Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 317366

Summary:

"restart now" after install should apply to all running instances

Product:

[Eclipse Project] Equinox

Reporter:

David Williams <david_williams>

Component:

Assignee:

P2 Inbox <equinox.p2-inbox>

Status:

CLOSED WONTFIX

QA Contact:

Severity:

enhancement

Priority:

CC:

irbull, krzysztof.daniel

Version:

3.6

Flags:

krzysztof.daniel: review? (pascal)

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

stalebug

Attachments:

Description	Flags
Patch proposition	krzysztof.daniel: review?

Description David Williams

2010-06-19 16:26:05 EDT

Not literally, but here's the use case: I often run with multiple instance of an IDE (each working on a different workspace), and just realized today that I can install something in one instance, and "restart" it, but there is no indication in the second instance that it too should be shutdown and restarted. 

Seems it'd be nice to get a pop up warning that said something similar to "The installation or configuration has been changed from another process. It is recommend that you restart now so all running instances are properly initialized". Or something to that effect. I should add, it'd be nice to come from the instance itself (not just a general change to the one message) as sometimes I forget if my multiple instances are the same instance or not (sometimes, for example, one might be Helios, the other might be Galileo). 
I suspect the perfect solution might even add a button to the one instance (when other running instances were known/detected, that allow the option "restart all now" ... but, that sounds pretty hard to do, and not sure its worth that much effort. 

Certainly not a big deal, as those running multiple instances is probably rare, and you could say they are "getting what they deserve" :) but ... seemed worth documenting the use-case in case this "restart" related code was ever improved.

Comment 1 Krzysztof Daniel

2013-08-09 04:24:40 EDT

It's not that rare use case. 

It happens every time when a Linux administrator updates Eclipse. I really like the idea that after calling yum update (as an administrator) my Eclipse (run as 
a user) will remind me that it needs to be restarted.

I'm rather afraid of cross-instance direct communication - Eclipses running from the same configuration don't have to be run on the same machine, and what's worse, it would open a security gap - how to find out who is really entitled to restart.

I think that a simple file hold in a configuration could be a good marker - any change to it would trigger a restart. algorithm for a job:

if (! .restart exists) create it.
watch two .restart files (user and master) and prompt on change

Now at the end of p2 job, it would be necessary to touch that .restart file.

Comment 2 Krzysztof Daniel

2013-08-09 07:41:11 EDT

Created attachment 234263 [details]
Patch proposition

Communication through file.

Comment 3 Lars Vogel

2019-11-27 07:21:35 EST

This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.