Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 343133 - Source files created in active task context are removed from context
Summary: Source files created in active task context are removed from context
Status: RESOLVED DUPLICATE of bug 341631
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-18 07:16 EDT by Stephen Williams CLA
Modified: 2011-05-09 15:21 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Williams CLA 2011-04-18 07:16:46 EDT
Build Identifier: 20100917-0705

I am adding a new feature to an application in the context of a Mylyn task and have just noticed that Eclipse has removed a Java source file I created this morning from the task context. The source file editor was still open, though, and, when I clicked on the editor tab, the source file reappeared in the Package Explorer.

Can you please confirm whether this behaviour is by design or is a bug? Specifically, will the automated context management ever remove source files from a task context that were created while the task context was active?

I recently posted a question on the Eclipse Community Forum asking for information on the automated context management implemented by Mylyn but, unfortunately, nobody replied to my post.

Reproducible: Always
Comment 1 Steffen Pingel CLA 2011-05-06 16:08:23 EDT
Stephen, please see bug 341631.

*** This bug has been marked as a duplicate of bug 341631 ***
Comment 2 Stephen Williams CLA 2011-05-09 03:45:24 EDT
Hi Steffen

I've read through the other bug report and I am not completely clear on whether or not Mylyn is behaving as I would expect it to behave.

To restate my question as simply as possible, files created / modified as part of a task do seem to be subject to decay and eventual removal from the task context - is this a bug or by design?

If it is by design, that is a problem as, if I add a new file or modify an existing file while a task is active, that file will always be relevant to that task and should never be automatically removed.

Regards

Stephen
Comment 3 Steffen Pingel CLA 2011-05-09 15:21:18 EDT
> To restate my question as simply as possible, files created / modified as part
> of a task do seem to be subject to decay and eventual removal from the task
> context - is this a bug or by design?

Yes, this is by design. Files do not actually get removed but the are filtered from focused views when their interest level falls below a certain threshold.

> If it is by design, that is a problem as, if I add a new file or modify an
> existing file while a task is active, that file will always be relevant to that
> task and should never be automatically removed.

Elements that are modified get a higher interest level than elements that are selected only so it takes much longer for their interest to decay below the threshold. Still, when working on a task for a long time you may end up editing many files and focused views would become overloaded without decay. Also see bug 178891 for a related discussion.

It would be helpful if you added your statements to bug 341631 so they doesn't get lost.