If the build itself modifies files checked out from CVS to the workspace (e.g.
by generating code), the CVS Polling will interpret this as change whereas
actually in CVS nothing has changed. Although it is not best practice to check
in generated code into CVS it would be nice to have an enhanced approach for
polling the CVS for changes.

My proposal is to use the CVS "rlog" command for that:

cvs -d ${CVSROOT} -Q rlog -S -d "${lastBuildDate}<" ${module}

A real world exeample could look like this:

cvs -d :pserver:anonymous@cvs.my_url.org/usr/local/cvs/my_repo -Q rlog -S -
d "2008-03-04 12:00<" my_module