{"shas":[["669d2983e65e8daa9355f1c9aa1671f3409ea644","3693a787e54bc89ddb1718ff55233ab515dc3d22@hotmail.com","log stuff to console if verbose is ON and running in VS","Iristyle"],["0e426f4ab60d14d47807b9284c2822100ce529e8","3693a787e54bc89ddb1718ff55233ab515dc3d22@hotmail.com","-- added two new configuration options - AppendToOutput and CondenseViolations (default: true)\n-- AppendToOutput will correctly munge together violations from one gendarme run to another, including any <file> nodes under <files>, <rule> nodes under <rules> and <target> nodes under <results><rule>\n-- CondenseViolations will group together <defect> nodes that are identical save for their innerText (description) -- really, this is just a refactoring of the code to allow configurable behavior","Iristyle"],["38cb7d97bb4bf34c6cbcea14d11cce1844d004ef","3693a787e54bc89ddb1718ff55233ab515dc3d22@hotmail.com","added in some additional error handling around Execute (solely for the purpose of diagnostics)\nreworked the logic around exitCodes, and handing off output to Visual Studio\nprocedure is now try to read generated xml file, and parse / dump to VS (honoring condense setting)\nthen if possible, try to munge xml files together\nthen condense violations if possible in resultant xml\nthen if the exitCode isn't 0, fail the task and log anything out of stdErr","Iristyle"],["e555eb1b4cba4adb572fae0e6a7bc795b14b42a0","3693a787e54bc89ddb1718ff55233ab515dc3d22@hotmail.com","reworked code to always parse output to make a determination if the task should be failed\nrefactored some other code","Iristyle"]],"repo":"Iristyle/GendarmeMsBuild","actor":"Iristyle","ref":"refs/heads/master","size":4,"head":"e555eb1b4cba4adb572fae0e6a7bc795b14b42a0","actor_gravatar":"c807a386363efa2147c76f4769cb24ee","push_id":26715846}