This project has moved and is read-only. For the latest updates, please go here.

Command Line Version

Dec 31, 2009 at 4:14 PM

I've just discovered this tool and love it! It's going to make cleaning up some legacy code much easier!

I'd like to be able to have it run as part of our Continuous Integration and nightly build process so that its report is mailed out to the developers/managers every morning. Are there any plans to extend functionality to allow this?

Jan 1, 2010 at 4:28 PM
Edited Jan 1, 2010 at 4:28 PM

Hi csuriano,

in fact this is already possible today. Clone Detective for Visual Studio builds upon the functionality provided by ConQAT for doing the actual analysis, which is a Java console application. It is triggered by the "CloneDetectiveInstallDir\ConQAT\bin\conqat.bat" file and all the necessary configuration can be supplied through command-line parameters. Depending on your settings in VS we pass a combination of -f, -s, and -p parameters to ConQAT. For instance, in the default configuration we run:

"CloneDetectiveInstallDir\ConQAT\bin\conqat.bat" -f "CloneDetectiveInstallDir\DefaultCloneDetection.cqa" -p "solution.dir=$(SolutionDir)" -p "output.dir=$(SolutionDir)" -p "output.file=$(SolutionName).CloneDetective.Clones.user" -p "clone.minlength=10"

Please note that the placeholder expansion is NOT performed by ConQAT, but by Clone Detective for VS - so if you want to run the detection from the command-line yourself you have to provide fully expanded property values.


Best regards,