Community
Participate
Working Groups
Build Identifier: The eclipsec.exe ( or eclipse.exe ) restarts itself with the same arguments when the cached bundle data in configuration folder is stale. This behavior makes it hard to work with scripting because the restarted process runs asynchronously and the first process which the script invokes exits before the restarted ends. And it seems there is no way to tell PID of the restarted process, so it is really hard for the script to detect if the eclipse-based command is completed or not. This is not a problem on unix/linux platform because it uses execvp() system call and it replaces the process image without kicking off a new process. ( according to eclipseNix.c#restartLauncher() ) Can you make it consistent with unix/linux's behavior? I know execvp() is probably not available on Windows, but it would be great if the first process waits until the restarted process ends. With that way, I can invoke eclipse from my script freely on both windows and unix/linux. Reproducible: Always Steps to Reproduce: 1. run eclipse 2. replace one or more plugins ( need to remove one of old plugins to force it restart) 3. run eclipse again -> it restarts with the same argument asynchronously
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. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
