java emma instr {-ip instrumentation path...} [-d directory] [-out metadata file] [-merge boolean] [-m output mode] [-ix filter patterns...]
[common options]
-ip, -cp, -instrpath instrumentation path...
-d, -dir, -outdir directory
-out, -outfile metadata file
-merge (y[es]|n[o])
-m, -outmode (copy|overwrite|fullcopy)
Specifies the instrumentation output mode. Valid values for this property are:
-ix, -filter filter patterns...
In-place instrument a certain subset of already compiled classes using overwrite mode and several coverage filters:
>java emma instr -m overwrite -ip out/classes -ix -*Test* -ix @myfilters.txt
Don't overwrite compiled classes that later need to go into official release jars (stay in copy mode). However, use incremental instrumentation for fast personal testing:
>java emma instr -merge y -ip out/classes -d out/classes-instrumented
Take all jars already produced by the product build and make test (coverage-enabled) copies of them:
>java emma instr -m fullcopy -merge no -ip out/Product.jar -d out-instrumented/
The default EMMA command line tool behavior is not to use System.exit() on exit unless an explicit -exit option is specified. If that is done, the error codes returned via System.exit() are as follows:
0 | Successful completion. |
1 | Failure due to incorrect option usage. This error code is also returned when command line usage (-h) is requested explicitly. |
2 | All other failures. |