Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [linuxtools-dev] TMF, RCP and workspace

Hi Xavier

I wasn't aware that the workspace can be re-used in an RCP. I expected the same behaviour than Eclipse where a workspace can't be opened multiple times at the same time. I guess we need to implemented the behaviour manually to avoid the problem that you and your
user faced.

I'll investigate whether it is possible to lock the workspace in the class org.eclipse.linuxtools.internal.tracing.rcp.ui.Application
where the workspace is created and opened. I'll let you know.

Bernd


On 04/04/2014 04:25 PM, Xavier Raynaud wrote:
Regarding multiple instances of the RCP running at the same time, I
guess we didn't really think about it... I just tried doing it, it opens
a separate instance, but the shared workspace makes it work weirdly. If
I open a trace in one, refreshing the other will show the newly added
trace, but the trace type won't be set in the second instance. There's
probably other bugs, that wasn't really tested.
There's other bugs:
Kalray RCP has the same behaviour as TMF RCP.
A customer of mine completely corrupts the workspace by running 2 instances of the RCP at the same time.
(according to log file, it seems files stored in .metadata/.plugins/org.eclipse.core.resources/ have been corrupted).
After that, it's no longer possible to start the RCP without deleting the workspace.

Is it even worth supporting it? Could we just prevent a second instance
from launching if the worskpace is already in use? (which normal Eclipse
does if you try to open a workspace already in use. I wonder why the RCP
doesn't do that).
I have the same questions :)

X
_______________________________________________
linuxtools-dev mailing list
linuxtools-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev



Back to the top