| Summary: | decouple monitor.ui from context.core | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P1 | CC: | krzysztof.daniel, shawn.minto, zephyrin.soh |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 360299 | ||
*** Bug 378343 has been marked as a duplicate of this bug. *** Migrated review: https://git.eclipse.org/r/#/c/5638/ Closing as part of backlog cleanup. Please reopen if you are working on this. |
The monitor.ui bundle should not have a direct dependency on context.core to avoid a cycle in the build dependency graph between Mylyn Context and Mylyn Commons and to improve reusability of the monitor components. To maintain backwards compatibility a new extension point in monitor.ui should be created that is invoked by AbstractUserInteractionMonitor: IInteractionEventProcessor { /** Sets properties of builder. */ void processNavigation(InteractionEventBuilder builder, String partId, Object targetElement, String kind, boolean contributeToContext) } InteractionEventBuilder { Kind kind; String structureKind; String handle; String originId; String navigatedRelation; IInteractionEvent createEvent(); }