document distributed coverage configuration options

For distributed per-test coverage to be enabled, the nested <distributedConfiguration/> element of clover-setup and clover-instr must be specified.

The simplest and quickest means to have distributed coverage collected is to add the <distributedcoverage/> element to clover-setup (or clover-instr) and then set the clover.server system property on the JVM running your tests:

Step 1 Configure Clover with distributed coverage.

<clover-setup>
  <distributedcoverage/>
</clover-setup>

Step 2 Set the clover.server system property on the test JVM

 <junit fork="true" forkmode="once" showoutput="true" printsummary="true">
                <sysproperty key="clover.server" value="true"/>
               ....
</junit>

NB: forkmode of perTest is currently unsupported.

<distributedConfiguration> accepts the following optional attributes:

• name the name of this configuration (tcp-config)
• port the port the test JVM should listen on (1198)
• host the host name the test JVM should bind to (localhost)
• timeout (number) the amount of time(ms) to wait before a connection attempt will fail (5000)
• numClients (number) the number of clients that need to connect to the test server before the tests will continue (0)
• retryPeriod (number) the amount of time (ms) to wait before attempting to reconnect in the advent of a network failure (1000)

NB: all attributes are optional.