Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323085 - Ability to defining the place where local mylyn are stored
Summary: Ability to defining the place where local mylyn are stored
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-18 16:21 EDT by Lars Vogel CLA
Modified: 2010-08-18 16:44 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2010-08-18 16:21:59 EDT
Currently local mylyn tasks are stored in the .metadata folder, e.g. .metadata/.mylyn/tasks.xml.zip

It would be great if it would be possible in future mylyn version to define a place where the tasks should be stored. This would allow to:

1.) Share local tasks between workspaces
2.) Share tasks via version control, e.g. git, between several machines
Comment 1 Steffen Pingel CLA 2010-08-18 16:29:08 EDT
This is already supported through setting the location of the data directory in the Preferences under Tasks > Advanced although this is not recommended and not safe to access concurrently from multiple workspaces.
Comment 2 Lars Vogel CLA 2010-08-18 16:33:38 EDT
Thanks. That is pretty cool & useful. May I asked what "not
safe to access concurrently from multiple workspaces" mean? Complete data loss?
Comment 3 Steffen Pingel CLA 2010-08-18 16:42:36 EDT
Mylyn does not do any explicit locking of files (but relies on workspace locking) so results are unpredictable when the data directory is accessed concurrently. Also note that some state is expected to be consistent across files, e.g. to track incremental synchronizations, so you may miss incomings and such when files are changed concurrently.
Comment 4 Lars Vogel CLA 2010-08-18 16:44:34 EDT
This should be fine for me, because I want to use the same set of task on multiple machines but I'm using only one machine at the time. 

Thanks for the clarification. I need to blog about this cool feature. :-)