[ http://jira.codehaus.org/browse/MPCLOVER-48?page=all ]
Vincent Massol closed MPCLOVER-48:
----------------------------------
Assign To: Vincent Massol
Resolution: Fixed
Fix Version: 1.11
Applied.Thanks Brendan.
Note: I've had a failure the first time I ran the clover plugin tests. I wasn't
able to reproduce it later on. I hope this is not related to any time-issue
while flushing coverage data to the database due to the change of policy.
> allow override of flushpolicy, flushinterval in <clover-setup>, change
> default values
> -------------------------------------------------------------------------------------
>
> Key: MPCLOVER-48
> URL: http://jira.codehaus.org/browse/MPCLOVER-48
> Project: maven-clover-plugin
> Type: Bug
> Versions: 1.10
> Reporter: Brendan Humphreys
> Assignee: Vincent Massol
> Priority: Critical
> Fix For: 1.11
>
>
> plugin.jelly hardwires Clover to use flushpolicy="interval"
> flushinterval="500". For large projects this can lead to a severe runtime
> performance impact because Clover tries to flush the coverage data to disk
> every 500msecs. I suggest exposing the flushpolicy and flushinterval as
> plugin properties, and also changing the default values:
> plugin.properties:
> maven.clover.flushpolicy=threaded
> maven.clover.flushinterval=5000
> plugin.jelly:
> <ant:clover-setup
> initstring="${maven.clover.database}"
> flushpolicy="${maven.clover.flushpolicy}"
> flushinterval="${maven.clover.flushinterval}">
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
