title: Is it possible to only run the JaCoCo maven plugin during the site lifecycle?
body: <p>Consider the follow build configuration:</p>
  
  <pre><code>  &lt;plugin&gt;
      &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
      &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt;
      &lt;configuration&gt;
        &lt;argLine&gt;${surefireArgLine}&lt;/argLine&gt;
        &lt;parallel&gt;all&lt;/parallel&gt;
        &lt;threadCount&gt;2&lt;/threadCount&gt;
      &lt;/configuration&gt;
    &lt;/plugin&gt;
    &lt;plugin&gt;
      &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
      &lt;artifactId&gt;maven-failsafe-plugin&lt;/artifactId&gt;
      &lt;configuration&gt;
        &lt;argLine&gt;${failsafeArgLine}&lt;/argLine&gt;
        &lt;parallel&gt;classes&lt;/parallel&gt;
        &lt;threadCount&gt;2&lt;/threadCount&gt;
      &lt;/configuration&gt;
    &lt;/plugin&gt;
    &lt;plugin&gt;
      &lt;groupId&gt;org.jacoco&lt;/groupId&gt;
      &lt;artifactId&gt;jacoco-maven-plugin&lt;/artifactId&gt;
      &lt;executions&gt;
        &lt;execution&gt;
          &lt;id&gt;pre-unit-test&lt;/id&gt;
          &lt;goals&gt;
            &lt;goal&gt;prepare-agent&lt;/goal&gt;
          &lt;/goals&gt;
          &lt;configuration&gt;
            &lt;destFile&gt;${project.build.directory}/jacoco-ut.exec&lt;/destFile&gt;
            &lt;propertyName&gt;surefireArgLine&lt;/propertyName&gt;
          &lt;/configuration&gt;
        &lt;/execution&gt;
        &lt;execution&gt;
          &lt;id&gt;post-unit-test&lt;/id&gt;
          &lt;phase&gt;test&lt;/phase&gt;
          &lt;goals&gt;
            &lt;goal&gt;report&lt;/goal&gt;
          &lt;/goals&gt;
          &lt;configuration&gt;
            &lt;dataFile&gt;${project.build.directory}/jacoco-ut.exec&lt;/dataFile&gt;
          &lt;/configuration&gt;
        &lt;/execution&gt;
        &lt;execution&gt;
          &lt;id&gt;pre-integration-test&lt;/id&gt;
          &lt;phase&gt;pre-integration-test&lt;/phase&gt;
          &lt;goals&gt;
            &lt;goal&gt;prepare-agent&lt;/goal&gt;
          &lt;/goals&gt;
          &lt;configuration&gt;
            &lt;destFile&gt;${project.build.directory}/jacoco-it.exec&lt;/destFile&gt;
            &lt;propertyName&gt;failsafeArgLine&lt;/propertyName&gt;
          &lt;/configuration&gt;
        &lt;/execution&gt;
        &lt;execution&gt;
          &lt;id&gt;post-integration-test&lt;/id&gt;
          &lt;phase&gt;post-integration-test&lt;/phase&gt;
          &lt;goals&gt;
            &lt;goal&gt;report&lt;/goal&gt;
          &lt;/goals&gt;
          &lt;configuration&gt;
            &lt;dataFile&gt;${project.build.directory}/jacoco-it.exec&lt;/dataFile&gt;
          &lt;/configuration&gt;
        &lt;/execution&gt;
      &lt;/executions&gt;
    &lt;/plugin&gt;
  </code></pre>
  
  <p>And reporting configuration:</p>
  
  <pre><code>  &lt;plugin&gt;
      &lt;groupId&gt;org.jacoco&lt;/groupId&gt;
      &lt;artifactId&gt;jacoco-maven-plugin&lt;/artifactId&gt;
      &lt;reportSets&gt;
        &lt;reportSet&gt;
          &lt;id&gt;JaCoCo-UnitTest&lt;/id&gt;
          &lt;reports&gt;
            &lt;report&gt;report&lt;/report&gt;
          &lt;/reports&gt;
          &lt;configuration&gt;
            &lt;dataFile&gt;${project.build.directory}/jacoco-ut.exec&lt;/dataFile&gt;
          &lt;/configuration&gt;
        &lt;/reportSet&gt;
        &lt;reportSet&gt;
          &lt;id&gt;JaCoCo-IntegrationTest&lt;/id&gt;
          &lt;reports&gt;
            &lt;report&gt;report&lt;/report&gt;
          &lt;/reports&gt;
          &lt;configuration&gt;
            &lt;dataFile&gt;${project.build.directory}/jacoco-it.exec&lt;/dataFile&gt;
          &lt;/configuration&gt;
        &lt;/reportSet&gt;
      &lt;/reportSets&gt;
    &lt;/plugin&gt;
  </code></pre>
  
  <p>The awesome part is <code>mvn clean site</code> works awesome, I get my reports. However, this now means that the JaCoCo agent is starting during the normal lifecycle, ie: <code>mvn clean install verify</code>. </p>
  
  <p>Is there a way to disable the JaCoCo agent during the normal lifecycle but not the site cycle?</p>