to ~/.m2/./ <<< but 'clover' classifier was lost In order to avoid this, you can use the instrument-test goal, which runs a forked lifecycle till the test phase. <<< file with double classifier was created - maven-install-plugin:2.5.2:install (default-install) moneybags - Installing. Example: clover:instrument + jar:test-jar + install:install - maven-jar-plugin:2.6:test-jar (default) moneybags - Building jar. In case your project creates artifacts with classifiers, it may happen that the 'clover' classifier will be lost and an instrumented artifact will be installed as non-instrumented one. Attention: Maven does not support multiple classifiers for an artifact.
CLOVER CONFIGURATOR 4.4 INSTALL
Thus running mvn install on a project where this instrument goal has been specified will run the build twice: once for building the project as usual and another time for instrumenting the sources with Clover and generating the Clover database. This will prevent instrumented sources to be put in production by error. This goal is forking a lifecycle because we don't want the Clover instrumentation to affect the main lifecycle build. Similarly, artifacts produced will have the 'clover' classifier. All instrumented classes will be stored in a separate directory.
This is a limitation of the site plugin which doesn't support reports.įork a custom build lifecycle in which all sources will be instrumented by Clover and next execute this lifecycle till the install phase. Note: This report mojo should be an and the clover:aggregate mojo shouldn't exist. If the project generating the report is a top level project and if the aggregate configuration element is set to true then an aggregated report will also be created. The generated report is an external report generated by Clover itself. Generate a Clover report from existing Clover databases. This mojo deletes the #cloverOutputDirectory} contents and the #snapshot} file used for test optimization. The clover:clean goal should be run directly from the command line, when you are developing using the clover test runner optimizer. The check is done on main Clover databases and also on merged Clover databases when they exist.
Verify Test Percentage Coverage (TPC) from an existing Clover database and fail the build if it is below the defined threshold. It's only there because the site plugin doesn't handle properly at the moment.
Aggregate children module Clover databases if there are any.
0 kommentar(er)
