The current version (0.6.7) of checkStreamForChanges that the polling-mechanism
uses in AccurevSCM.java triggers on changes in transactions of the "dispatch"
kind, in other words, issue-related changes and not code or "filesystem" related
changes (and the result is unnecessary builds).

This is due to that the accurev hist command that is used to query AccuRev for
changes is unable to exclude transactions of the dispatch-kind and is only able to
include transactions of a special kind.