Hi, Just found a new use case for the clover plugin. This is something required for converting the cargo m1 build to m2.
Most Cargo tests are functional tests and they call container code (running in the same JVM). We would like that coverage data reports the code covered inside the container. Thus we need to add the clover jar and license inside the WAR/EAR that we deploy in the containers. To do this, our junit tests need to have the paths to the clover jar and the clover license file. In m1, we're passing this information by getting it directly from the clover plugin... I'm suggesting to do the following to support this use case in m2: - Modify the Clover plugin so that it creates 2 system properties (clover.jar and clover.license for example) that it will (somehow) add to the surefire configuration properties. This is consistent with the current approach of exposing basedir and localRepository system properties in the surefire plugin. WDYT? Is it technically possible to add properties to a plugin's configuration properties object? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
