Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Setting clover.initstring doesn't seem to be working for me

Thomas Young September 18, 2012

I am attempting to deploy an instrumented war file (and clover.db file) to a webserver, record coverage data from manual testing, and then copy the clover database back to the machine that generated it to generate a report. I have gotten this to work when I specify the clover database location at *build* time using the maven option:

-Dmaven.clover.cloverDatabase=/data/stingray-coverage/clover.db

The problem is that I would like to do this at runtime to avoid having to have the build server and the webserver use exactly the same directory. I have tried using the clover initstring property:

-Dclover.initstring=/data/stingray-coverage/clover.db

as an option for Tomcat, but I still see the following in the logs and no coverage data is recorded:

ERROR: CLOVER: Unable to load the coverage database at "/data/hudson/home/jobs/thomas-test-job2/workspace/projects/redfin.commerceWeb/target/clover/clover.db"

Any insight you could give into what is going wrong would be appreciated.

1 answer

1 accepted

0 votes
Answer accepted
Thomas Young September 18, 2012

Ah, nevermind. I wasn't setting the variable properly with tomcat (figures I find that out just after I post this).

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events