Is it a good idea to turn off resource monitoring? Is
there any chance that if I do that, locations that I visit won’t be added
to the active task context?
I’m unclear on the benefits of resource monitoring.
In my organization, refreshes invariably pollute the context of an active task
with hundreds or thousands of irrelevant items that happened to have been
updated by a recent source-control checkout and build. Why might I even
want files that I haven’t visited or designated as “interesting”
to be added to my task context?
A typical developer workspace in my org has many different
projects, 50 or so. We use a source control system that isn’t yet
integrated with Mylyn. A developer updates his workspace by running a
source control update from the command line, launching an external tool via
Eclipse that usually generates some files, and then refreshes the workspace,
triggering a build. There are over a hundred developers, so each update
usually brings many uninteresting files into the active task context. As
I see it, whatever benefits there might be from resource monitoring are
outweighed by the drawbacks.
So I’ve experimented with turning off resource
monitoring by adding
ResourcesUiBridgePlugin.getDefault
().setResourceMonitoringEnabled ( false );
to the lazyStart() method of my plugin class. Right
now I see the desired behavior – when I visit locations, they are added
to the context, as normal; no external changes show up in the task
context after I run the update from source control via the command line and
then run the external tool from within Eclipse. However, a couple of
days ago, when I installed a version of my connector with what I believe was the
same change, visited locations were _not_ added to the context.
Any idea why Mylyn might have behaved that way? Does detection and
addition to the context of visited locations in any way depend on resource
monitoring?
Larry Edelstein
Senior Member of Technical Staff
Salesforce.com
ledelstein@xxxxxxxxxxxxxx