| Summary: | [context] automatically expanded context to elements with compile errors | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Miles Parker <milesparker> |
| Component: | Mylyn | Assignee: | Mylyn Inbox <mylyn-inbox> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | shawn.minto |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Miles Parker
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 |