Message-ID: <490189472.7623.1409687918854.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_7622_649883502.1409687918854" ------=_Part_7622_649883502.1409687918854 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Exclude files from analysis based on a cutoff date threshold (or a cutof= f period). Any source file that was last modified prior to the configured c= utoff date is excluded. This can be useful when you want to analyze the wor= k done on an existing code base and measure the quality of new code/changes= only. This way previous phases of the project will not impact the analysis= .
The cutoff date or cutoff period can be set at global or project le=
vel: go to Settings > General Settings > Cutoff and set either t=
sonar.cutoff.date or the
The plugin currently relies on the file system date which is very random= and will be difficult to reproduce on a different machine. The next step i= s really to get the information from SCM.
|=20||SONA= RPLUGINS-731=20||Create initial vers= ion that looks at date on the file system=20||=20|
|=20||SONA= RPLUGINS-698=20||Allow to exclude so= urces from code analysis based on cutoff date=20||=20|