I have a build using 2 subversions module
the first one contains the code base (on a branch), and is set to check out to HEAD
the second one contains the build scripts and is set to use a specific revision using the @NNN feature in the svn url.
It works great so far.

this build is also setup to use SCM polling (obviously for the first module).
the problem is, since i'm using a specific revision for the second module, the polling think there's always something new.

in the scm polling log:
svn://svnserver/deployment/scripts is at revision 185,800
(changed from 184,375)

and in the module i have as url : svn://svnserver/deployment/scripts@184375

schedule for scm polling is */15 * * * *

expected behavior : polling should not check for changes when using a specific revision, since it won't update anyway.