I saw that when I configure XML, PDF, or HTML... things work as expected for enabling/disabling. When I configure JSON to be on, I saw no clover.json as I saw clover.xml and clover.pdf.
So then I went to debug with a line like this:
java -Dclover.license.path=/Users/dstein/Desktop/clover.lic -cp "/Users/dstein/.m2/repository/com/atlassian/clover/clover/4.1.2/*" com.atlassian.clover.reporters.json.JSONReporter -i target/clover/clover.db -o clover_json -d
There were zero errors. It did create a folder and then put a lot of JS files in. They all looked like JSONP, where they expect processClover to be some method that is passing in all the JSON.
So is JSON actually meant to be put into a page? Am I missing something here?
Hey Grzegorz, thanks for this reply. Never ran into that documentation while looking around. You did answer my question about being put into a page though. This option should be called JSONP moreso than JSON. The documentation shows it's intended to be be put into an HTML page, with a callback defined, to get the results.
Therefore if I want to run a script against results, I need to use the XML output even though it's more desirable to just parse JSON.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot