Community
Participate
Working Groups
Across all of the Mylyn supported content types I think it would be really nice to support the following Story: A user is making changes to some artifact within an active context. On save, a builder discovers and marks an error in some other artifact. Based on this interaction, the active context's focus could then be expanded to include the files and any new enclosing projects. Discussion: In my experience, the biggest challenge to adopting Mylyn is the effort involved in expanding focus, and anything that Mylyn can do to infer appropriate widening of context would really address that. This seems like it would automate a user behavior pattern that is common, if not typical. I break something and I want to see what I've broken -- if I'd know what I was going to break, I probably wouldn't have broken it. This would also address a significant issue with Mylyn use currently.. because much of the workspace is hidden, I might not even *know* that I had broken something downstream until I tried to launch the application or run a build.
One note I forgot. There would have to be some kind of mechanism for providing a threshold for when such context additions would be triggered. In the case where I've just broken dozens of downstream artifacts, I wouldn't want to have these all added to the context. Still, I'd want to know that I had broken stuff, so perhaps they could be revealed at the project level. I'm also not sure if there is a distinction between revealing some subset of entire workspace and actually adding that new subset to the context. In the latter case, I'm really just talking here of revealing the new errors.
Shawn, wasn't some of that implemented at some point (maybe still in the Incubator)?
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
