search

perforce / sonar-scm-perforce

SonarQube Perforce plugin
6 stars 23 forks source link

Fix of PerforceBlameCommand to analyse "have" revision #2

Closed halfwhite closed 9 years ago

halfwhite commented 9 years ago

Before the change blame was return for the head revision. For big projects files in perforce could be changed during analysis. That was the reason why analysed file had different numbers of lines then the file a blame information was returned for. Analysis failed and could not finished successfully because of that.

The change sets for a file spec "have" revision so that the blame information is returned for the files that are in perforce workspace during analysis.

henryju commented 9 years ago

Cool! Many thanks! I was not aware of this feature (IFileSpec.HAVE_REVISION).

halfwhite commented 9 years ago

:) Waiting for the release of the plugin :)

Regards

On 22 January 2015 at 12:20, Julien HENRY notifications@github.com wrote:

Cool! Many thanks! I was not aware of this feature (IFileSpec.HAVE_REVISION).

— Reply to this email directly or view it on GitHub https://github.com/SonarCommunity/sonar-scm-perforce/pull/2#issuecomment-70992069 .

henryju commented 9 years ago

Please give me a +1 on the SonarQube dev mailing list. The vote is in progress but I didn't receive any "official" vote. http://sonarqube.15.x6.nabble.com/sonar-dev-VOTE-Release-Perforce-Plugin-1-0-td5031208.html