Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366925 - Per-project store of local tasks (aka a light version of the distributed issue tracking)
Summary: Per-project store of local tasks (aka a light version of the distributed issu...
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-16 05:28 EST by Matěj Cepl CLA
Modified: 2012-03-07 02:09 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matěj Cepl CLA 2011-12-16 05:28:23 EST 
Build Identifier: 20110916-0149

Would it be possible to configure Mylyn Local Tasks so that they would use for storage of data a directory in the project directory (e.g., .mylyn or in a subdirectory in .settings/)?

With that I could keep my data in a git repository together with the project data and make a light version of the distributed issue tracker.

Reproducible: Always

Steps to Reproduce:
1.see above
2.
3.
Comment 1 Steffen Pingel CLA 2011-12-16 11:07:24 EST 
Even though it's not recommended you change the location of the data store under Preferences >Mylyn > Tasks > Advanced: http://wiki.eclipse.org/index.php/Mylyn_FAQ#What_if_I_use_multiple_workspaces.3F.
Comment 2 Matěj Cepl CLA 2011-12-16 16:39:02 EST 
But that's per-workspace, not per-project, right? So, I would have to use one workspace for each project?

If you want to say WONTFIX, just say so.
Comment 3 Steffen Pingel CLA 2011-12-17 04:08:11 EST 
Yes, that only works for the entire data store for the workspace. We don't have plans to support multiple local repositories at this point.
Comment 4 Steffen Pingel CLA 2012-03-07 02:09:45 EST 
A related discussion about distributed issue tracking is on bug 367719.