Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 191867

Summary:	Allow to store task context info within projects
Product:	z_Archived	Reporter:	Eugene Kuleshov <ekuleshov>
Component:	Mylyn	Assignee:	Mik Kersten <mik.kersten>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	wmitsuda
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Eugene Kuleshov

2007-06-10 19:02:30 EDT

Current approach with storing task context outside of the project code works ok for context sharing, but it makes really difficult to make existing contexts accessible for facilities like search and refactoring. Refactoring is particularly important, because it has huge impact on context data, i.e. renaming and moving stuff.

It would make sense to use some kind of aggregated context, that would pickup and store its pieces from each project. So, that data will be always available for refactoring participants and will also make it easier to share contexts on repositories that don't have rich Mylar connectors.

Comment 1 Willian Mitsuda

2007-06-10 20:34:41 EDT

There are already bugs opened regarding the refactoring problem, like bug#164058.

Comment 2 Mik Kersten

2007-06-11 18:55:46 EDT

Task contexts are not resources that should be visible to the end user.  As such the plan is to give them a custom refactoring participant.  We could then also make the corresponding index searchable.  Also, they are a per-user structure not a per-project.  Way back we used to store them in a .context folder of a project but it turned out annoying for several reasons, one of which was that the folder had to have a folder for each user.  So we opted for sharing via task repositories. 

Since the main use case seems to be refactoring I'll mark this as a duplicate of bug 164058.  Search is bug 137486.  Willian's bug is also relevant.

*** This bug has been marked as a duplicate of bug 164058 ***

Comment 3 Eugene Kuleshov

2007-06-11 19:07:09 EDT

Mik, it is not a duplicate and refactoring is not only use case for this. The major problem with bug 164058 is that id does not have foundation for resolving it and I currently don't see any other options to make sure that every user would have all context data available for being updated during refactoring.

Feel free to close it as won't fix if you feel strongly against storing partial project-specific context data within project. Also, I would think that context of the same task should be the same between multiple users participating into such task. It is like a wiki change history, though you may want to add user identity to the context...

Comment 4 Mik Kersten

2009-07-24 00:48:31 EDT

No plans to do this.