Can I specify the clover database on the command line?

[Mark Brewster]

I can create a clover.db through our 'build' job.  To make this db available to subsequent Jenkins jobs, I copy this database file to the /tmp folder. 

Since I can specify the license file on the command line using -Dmaven.clover.licenseLocation=/path/to/license, I assumed I would be able to specify the clover.db file on the command line such as -Dmaven.clover.cloverDatabase=/path/to/clover.db

However, when I run an integration test job using the following command line.  

mvn -Dmaven.clover.licenseLocation=/path/to/license -Dmaven.clover.cloverDatabase=<path to db> -Pintegration clover2:clover 

I'll see at the bottom of the output. 

'No clover database specified no report generated'

I don't understand.

[Marek Parfianowicz]

This should work. Clover searches for a database in the following locations:

• first it looks for a single module database
  • as specified in the -Dmaven.clover.cloverDatabase
  • or in its default location (target/clover/clover.db)
• next it looks for a merged database
  • as specified in the -Dmaven.clover.cloverMergeDatabase
  • or in its default location (target/clover/cloverMerge.db)

If file is not found in none of these locations, it prints a warning "No Clover database found, skipping report generation".

Please run a build with debug logging (mvn -X) and check if you don't define the -Dmaven.clover.cloverDatabase twice or you don't override it.