I use an instrumented build to collect test coverage data. I move the collected data to another system to generate the reports and use the <sourcepath> setting to point to my source code on the system where I generate the reports because it is different than when the instrumented build is created. I see a lot of errors in my ant log when building the report that look like this:
[clover-report] looking for /path/from/sourcepath/D:/path/from/instrumented/build/file.java: not found
where file.java is most if not all of my .java files.
It looks like instead of just the filename, the fully qualified path gets used. If it would have used the sourcepath/file.java it would find the file. I did a strings on the coverage.db file and see the D: before all of the files there also.
In the html report all of the links to drill down into the classes tries to go to a file at D: which does not exist on the system and the in the top of the report is says "Statistics for file D:\...
I am not sure how to fix this or what is wrong and I have not been able to find anything in the doc that is obfious to me. I am new to most of this. Is this something that I need to use the fullyQualifiedJavaLang option to deal with?
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs