Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-1670

A way to skip clover entirely (i.e including forked lifecycle)

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      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 ?

      Attachments

        Activity

          People

            mparfianowicz Marek Parfianowicz
            59be85ca750f Gregory Joseph
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: