Community
Participate
Working Groups
For some strange reason Mylyn occasionally decides to unfold a large number (~50) of my eclipse projects (maybe, because they are indeed related - they all are part of the eclipse COSMOS project - or maybe because I usually update them from CVS in a single go and Mylyn just thinks they are all part of my current "focus" - whatever). I then always have to close all these projects so that I can get an grip on them again which is actually a quite annoying task and I would really like Mylyn to stop this nonsense! So, either Mylyn should be fixed and recognize, that certain operations like doing SVN or CVS update have nothing to do with "context" or then it should provide some "collapse all"-button or -context menu entry, so that one can at least quicker clean up the debris after its misdeeds. Michael
Michael: as far as I can tell you are hitting bug 120499, which causes newly-created elements to be added to the task context. The work-around is listed at: http://www.eclipse.org/mylyn/tips/ (deactivate the task before checking out projects or doing a big synchronization). If this is not the case for you, or if I have misunderstood, please comment or reopen this bug. Also, note that you can select multiple elements and use Remove from Context in the Package Explorer's popup menu. *** This bug has been marked as a duplicate of bug 120499 ***
It seems to me that disregarding this issue with "deactivate task" workaround is probably not very useful to the end users. I've been asked related questions at my Eclipse DemoCamp presentation. See some summary http://www.jroller.com/eu/entry/mylyn_tips_and_tricks
(In reply to comment #1) Yes - this very much seems to be the case here. Same cause and same effect as discussed there. (In reply to comment #2) Thanks for the pointer. Already printed it out to be my next "bus ride reading material" :-) In general: I guess, I need to adopt a few new habits re. work style (like the suggested switch to a temp. task, when one gets interrupted or does such "non-interesting" updates etc.), but that seems manageable. One only needs to think about it... Thanks both!
(In reply to comment #2) > It seems to me that disregarding this issue with "deactivate task" workaround is > probably not very useful to the end users. Eugene: please note that a "workaround" means something we suggest users do while we figure out how to address a particular bug or usability problem.
