Community
Participate
Working Groups
The activity monitoring in MonitorUIPlugin is activated on each startup regardless of task activation or other consumers of timing events. To avoid unnecessary load activity monitoring should only run on demand. Additionally the initialization in MonitorUiPlugin.start() should be reviewed. More detailed discussion is on bug 192084 (In reply to comment #19) > (In reply to comment #18) > > (In reply to comment #14) > > > Please note that the patch causes the activity job to always get started. > > > Previously that required at least a single task activation. Rob, can you > > > explain the reason for this change? > > We should consider adding this back. This was a side effect of simplification > > but comes at the cost of the job allocation for those who don't activate > tasks. > > The job should run if there is an interested consumer, e.g. time tracking or > task list sync. It should not be based on a preference. Agreed. I'll look at adding this now. As for the failing unit test, when run with TEST_MODE = true, the necessary bits run in the the ui job correctly which results in correct startup and sequence of activity events. Thoughts on how to test this? Can we run a single test as 'non-test' mode?
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
