If I try to skip clover (say, for a submodule of a multi-module project where clover is enabled in the parent), I can do this:

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>com.atlassian.maven.plugins</groupId>
          <artifactId>maven-clover2-plugin</artifactId>
          <configuration>
            <skip>true</skip>
          </configuration>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

However, the whole forked lifecycle is still executed; it seems Clover only skips the instrumentation of code, but still executes the various other phases. This feels highly unnecessary. Any way around this ?