Community
Participate
Working Groups
Build Identifier: 20110615-0604 I would like a new Mylyn preference that, when enabled, prevents Mylyn from removing resources (specifically Java source code files) that I have added to / edited within a context. Only resources I have looked at are subject to removal. Without this preference, I cannot begin to use the task-focused UI because the inflexible behaviour of the automatic task context management prevents me from working in the way that I am accustomed to. This enhancement request is a follow on from comments I added to Bug 341631. Reproducible: Always
Two points ... i) I'm not sure what the process is that transforms an enhancement request into a new feature but, if it is the case that my enhancement request must garner sufficient public votes before it will be selected for development effort, I suspect it will never see the light of day. The problem is, voters are likely to be existing users who, presumably, have no significant issues with the existing behaviour. Those people who do have significant issues with it and do not use Mylyn because of those issues, people like myself, are unlikely to find themselves in Bugzilla voting for my enhancement request. ii) I found another developer in my office this week who has also tried to use Mylyn. I asked him how he got on and he said he had stopped using it because he found the automated context management unhelpful and confusing. He just could not understand why it might decide that a Java source file that had been added to a task context or one that had been changed while the task context was active was not relevant to that task. As this is exactly the issue I have with Mylyn, I thought I must mention it.
We need to come to a consensus on how the decay behaviour could be improved. Let's keep the discussion on bug 341631. *** This bug has been marked as a duplicate of bug 341631 ***
