Community
Participate
Working Groups
I'm using a shared .mylar data directory, but I'd like to isolate the sharing to queries only. In other words, I'm looking for the ability to have separate contexts for each workspace. This way, they can all share the same task list, but they have individual context histories. As it stands right now, when I close one Eclipse instance but leave one task active, my other workspaces - especially the ones that represent different projects, not just different lines of development on the same project - open with the same active task and "attempt" to re-open the context too, which won't work most of the time. if I still need to share the context for some reason (maybe different lines of development haven't changed the packaging structure or the module layout), then I can still use the attach/retrieve context mechanism.
It is really sounds strange to me to have same tasks with different contexts. I'd use separate data folders if I'd need to keep contexts separate. As of saving active task inside data directory, there maybe already issue for that (unless I forgot to fill it in).
Well, OK, not seperate contexts for the same task, but at least a workspace-specific active task context. This way, I can have multiple workspaces open without them colliding. So, at least I got the summary/title right. ; )
I don't think Mylar will handle situation when several Eclipse instances are writing into the same task store. You are in a great risk of loosing your task data. But I do agree that info about currently active task should be stored in workspace settings.
Well, I haven't had any issues yet. Maybe it's because I stagger the startup of each one, thus none of them ever collide and try to write to the store at the same time? Regardless, if this could be an issue, perhaps something should be mentioned in the FAQ that it's strongly suggested to only use one Eclipse instance at a time when working with a shared data dir.
(In reply to comment #4) > Maybe it's because I stagger the startup of each one, thus none of them ever collide and try to write to the store at the same time? On every single change the whole context is written to disk, but as far as I know it is never read back. So, if two instances will be updating tasks at the same time I don't even want to think what exactly going to happen with those tasks.
Hmm, I see what you're saying. I guess I haven't seen any issues with the task list itself, but perhaps I should check how my old contexts are doing.
We need to address this as part of the multiple-workspace support improvements. Until then using a single data directory with multiple active workspaces is not recommended for the reasons discussed. *** This bug has been marked as a duplicate of bug 130658 ***
