pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>de.scrum-master.spock</groupId>
  <artifactId>spock-powermock</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <organization>
    <name>Scrum-Master.de - Agile Project Management</name>
    <url>https://scrum-master.de</url>
  </organization>

  <properties>

    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

    <maven.compiler.source>8</maven.compiler.source>
    <maven.compiler.target>8</maven.compiler.target>
    <!--
      Enable automatic use of Parrot parser for Groovy-Eclipse in order to compile e.g. Groovy 3 Java-style lambdas.
      Same as '<fork>true</fork>' for Maven Compiler and an alternative to '-Dgroovy.antlr4=true'. See also:
        https://github.com/groovy/groovy-eclipse/issues/1107
        https://github.com/groovy/groovy-eclipse/issues/1137
    -->
    <maven.compiler.fork>true</maven.compiler.fork>

    <!--
      Defined by build-helper:rootlocation.
      Unfortunately, for IntelliJ IDEA we still need "-DprojectRootDir=..." in <projectRootDir>/.mvn/jvm.config.
    -->
    <!--suppress UnresolvedMavenProperty -->
    <projectRootDir>${rootlocation}</projectRootDir>

    <!-- See org.spockframework:spock-core, entry 'junit-bom' and then check the used platform in the JUnit BoM -->
    <version.junit>5.8.1</version.junit>
    <version.junit-platform>1.8.1</version.junit-platform>

    <version.testng>7.1.0</version.testng>

    <version.groovy>4.0.6</version.groovy>
    <version.groovy-eclipse-compiler>3.8.0</version.groovy-eclipse-compiler>
    <version.groovy-eclipse-batch>4.0.6-02</version.groovy-eclipse-batch>

    <version.spock>2.3-groovy-4.0-SNAPSHOT</version.spock>

    <!-- 2.0.7 contains an important bug fix making '@Rule PowerMockRule' usable from Spock -->
    <version.powermock>2.0.9</version.powermock>

    <version.easymock>4.0.1</version.easymock>

    <version.jmockit>1.49</version.jmockit>

    <version.surefire>3.0.0-M7</version.surefire>

    <instrumented-jre.jar>
      ${projectRootDir}/instrument-jre-classes/target/instrument-jre-classes-${project.version}.jar
    </instrumented-jre.jar>

    <bytebuddy.version>1.12.7</bytebuddy.version>
    <bytebuddy.jar>
      ${settings.localRepository}/net/bytebuddy/byte-buddy/${bytebuddy.version}/byte-buddy-${bytebuddy.version}.jar
    </bytebuddy.jar>

    <sarek.version>1.0-SNAPSHOT</sarek.version>
    <sarek.jar>
      ${settings.localRepository}/dev/sarek/sarek-special/${sarek.version}/sarek-special-${sarek.version}.jar
    </sarek.jar>
  </properties>

  <repositories>
    <repository>
      <id>sonatype-snapshots</id>
      <url>https://oss.sonatype.org/content/repositories/snapshots/</url>
      <releases>
        <enabled>false</enabled>
      </releases>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
    </repository>
  </repositories>

  <pluginRepositories>
    <pluginRepository>
      <id>groovy-plugins-release</id>
      <url>https://groovy.jfrog.io/artifactory/plugins-release</url>
    </pluginRepository>
    <pluginRepository>
      <id>apache-snapshots</id>
      <url>https://repository.apache.org/snapshots/</url>
      <releases>
        <enabled>false</enabled>
      </releases>
      <snapshots>
        <enabled>true</enabled>
      </snapshots>
    </pluginRepository>
  </pluginRepositories>

  <build>
    <pluginManagement>

      <plugins>

        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-compiler-plugin</artifactId>
          <version>3.8.1</version>
          <configuration>
            <source>${maven.compiler.source}</source>
            <target>${maven.compiler.target}</target>
            <encoding>UTF8</encoding>
            <compilerId>groovy-eclipse-compiler</compilerId>
          </configuration>
          <dependencies>
            <dependency>
              <groupId>org.codehaus.groovy</groupId>
              <artifactId>groovy-eclipse-compiler</artifactId>
              <version>${version.groovy-eclipse-compiler}</version>
            </dependency>
            <dependency>
              <groupId>org.codehaus.groovy</groupId>
              <artifactId>groovy-eclipse-batch</artifactId>
              <version>${version.groovy-eclipse-batch}</version>
            </dependency>
          </dependencies>
        </plugin>

<!--
        <plugin>
          <groupId>org.codehaus.groovy</groupId>
          <artifactId>groovy-eclipse-compiler</artifactId>
          <version>${version.groovy-eclipse-compiler}</version>
          <extensions>true</extensions>
        </plugin>
-->

        <!--
          Below version 2.22.0 Surefire will not execute Spock 2 tests,
          but e.g Maven 3.5.2 and 3.6.0 use Surefire 2.12.4 by default.
        -->
        <plugin>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>${version.surefire}</version>
          <configuration>
            <!-- Do not reuse forked VMs because of potentially unexpected instrumentation bleed-over -->
            <reuseForks>false</reuseForks>
            <argLine>
              -Dfile.encoding=UTF8

              <!--
                On Java 9+ you cannot prepend to the bootstrap classpath anymore, only append.
                Instead, you can patch each module separately via:
                  -'-patch-module <module>=<file>(<pathsep><file>)*
                See http://openjdk.java.net/jeps/261#Patching-module-content.
              -->
              <!-- Java < 9 -->
<!--               -Xbootclasspath/p:${instrumented-jre.jar}-->
              <!-- Java 9+ -->
              --patch-module java.base=${instrumented-jre.jar}

              <!-- Java 9+: needed for hot-attaching agents (e.g. PowerMock) -->
              -Djdk.attach.allowAttachSelf=true

              <!-- Java 16+ -->
              --add-opens java.base/java.lang=ALL-UNNAMED
              --add-opens java.base/java.lang.ref=ALL-UNNAMED
              --add-opens java.base/java.io=ALL-UNNAMED

              <!---javaagent:"${settings.localRepository}/org/jmockit/jmockit/${version.jmockit}/jmockit-${version.jmockit}.jar"-->

              <!--
                The combination Sarek + PowerMock on JDK 8 only works when using the Java agent,
                not the Spock or TestNG plugins (https://github.com/raphw/byte-buddy/issues/1191).
                On JDK 9+, it also works with the plugins.
              -->
<!--              -javaagent:"${sarek.jar}=UnFinal,verbXXXose"-->
            </argLine>
            <systemPropertyVariables>
              <!-- Necessary for SarekJUnit5Extension auto-detection -->
              <junit.jupiter.extensions.autodetection.enabled>true</junit.jupiter.extensions.autodetection.enabled>
            </systemPropertyVariables>
          </configuration>
        </plugin>

        <!--
          Below version 2.22.0 Failsafe will not execute Spock 2 tests,
          but e.g Maven 3.5.2 and 3.6.0 use Failsafe 2.12.4 by default.
        -->
        <plugin>
          <artifactId>maven-failsafe-plugin</artifactId>
          <version>${version.surefire}</version>
          <configuration>
            <!-- Do not reuse forked VMs because of potentially unexpected instrumentation bleed-over -->
            <reuseForks>false</reuseForks>
            <argLine>
              <!---Dfile.encoding=UTF8-->
              <!---javaagent:"${settings.localRepository}"/org/jmockit/jmockit/${version.jmockit}/jmockit-${version.jmockit}.jar-->
            </argLine>
            <systemPropertyVariables>
              <!-- Necessary for SarekJUnit5Extension auto-detection -->
              <junit.jupiter.extensions.autodetection.enabled>true</junit.jupiter.extensions.autodetection.enabled>
            </systemPropertyVariables>
          </configuration>
          <executions>
            <execution>
              <goals>
                <goal>integration-test</goal>
                <goal>verify</goal>
              </goals>
            </execution>
          </executions>
        </plugin>

        <plugin>
          <artifactId>maven-enforcer-plugin</artifactId>
          <version>3.0.0-M3</version>
          <executions>
            <execution>
              <id>enforce-versions</id>
              <goals>
                <goal>enforce</goal>
              </goals>
              <configuration>
                <rules>
                  <!-- We use compiler source/target 8 -> enforce Java 8+ -->
                  <requireJavaVersion>
                    <version>1.8</version>
                  </requireJavaVersion>
                  <!-- maven.multiModuleProjectDirectory: introduced in 3.3.1, important bug fix in 3.3.9 -->
                  <requireMavenVersion>
                    <version>3.3.9</version>
                  </requireMavenVersion>
                </rules>
              </configuration>
            </execution>
          </executions>
        </plugin>

        <plugin>
          <groupId>org.codehaus.mojo</groupId>
          <artifactId>build-helper-maven-plugin</artifactId>
          <!-- Version 3.2.0 fixes goal 'rootlocation' -->
          <version>3.2.0</version>
        </plugin>

      </plugins>
    </pluginManagement>

    <plugins>

      <plugin>
        <artifactId>maven-enforcer-plugin</artifactId>
      </plugin>

      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>build-helper-maven-plugin</artifactId>
        <executions>
          <execution>
            <id>set-project-root-dir</id>
            <phase>validate</phase>
            <goals>
              <!--
                TODO:
                  Investigate Directory Maven Plugin as an alternative, also with regard to IDEA compatibility
                  (needs .mvn/jvm.config?). https://github.com/jdcasey/directory-maven-plugin#highest-basedir-goal
              -->
              <goal>rootlocation</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

    </plugins>

  </build>

  <dependencyManagement>
    <dependencies>

      <!-- Groovy -->
      <dependency>
        <groupId>org.apache.groovy</groupId>
        <artifactId>groovy</artifactId>
        <version>${version.groovy}</version>
        <scope>test</scope>
      </dependency>

      <!-- Spock -->
      <dependency>
        <groupId>org.spockframework</groupId>
        <artifactId>spock-core</artifactId>
        <version>${version.spock}</version>
        <scope>test</scope>
      </dependency>
      <!--
        JUnit 4 compatibility layer is needed for @Rule PowermockRule.
        Please keep even though reported as unused by dependency:analyze!
      -->
      <dependency>
        <groupId>org.spockframework</groupId>
        <artifactId>spock-junit4</artifactId>
        <version>${version.spock}</version>
        <scope>test</scope>
      </dependency>
      <!-- JUnit 4 version used by Spock, needed for @Rule PowermockRule -->
      <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <version>4.12</version>
        <scope>test</scope>
      </dependency>

      <!-- PowerMock -->
      <dependency>
        <groupId>org.powermock</groupId>
        <artifactId>powermock-core</artifactId>
        <version>${version.powermock}</version>
        <scope>test</scope>
      </dependency>
      <!-- PowerMock Mockito 2 API -->
      <dependency>
        <groupId>org.powermock</groupId>
        <artifactId>powermock-api-mockito2</artifactId>
        <version>${version.powermock}</version>
        <scope>test</scope>
      </dependency>
      <!-- PowerMock EasyMock API -->
      <dependency>
        <groupId>org.powermock</groupId>
        <artifactId>powermock-api-easymock</artifactId>
        <version>${version.powermock}</version>
        <scope>test</scope>
      </dependency>
      <!-- EasyMock version used by PowerMock -->
      <dependency>
        <groupId>org.easymock</groupId>
        <artifactId>easymock</artifactId>
        <version>${version.easymock}</version>
        <scope>test</scope>
      </dependency>

      <!--
        JUnit 4 agent-based @Rule PowermockRule is the only working option in Spock 2,
        but due to https://github.com/raphw/byte-buddy/issues/1191 only on JRE 9+
      -->
      <dependency>
        <groupId>org.powermock</groupId>
        <artifactId>powermock-module-junit4-rule-agent</artifactId>
        <version>${version.powermock}</version>
        <scope>test</scope>
      </dependency>

      <!-- JMockit agent for mocking final classes/methods -->
      <dependency>
        <groupId>org.jmockit</groupId>
        <artifactId>jmockit</artifactId>
        <version>${version.jmockit}</version>
        <scope>test</scope>
      </dependency>

      <dependency>
        <groupId>de.scrum-master</groupId>
        <artifactId>bytebuddy-agent</artifactId>
        <version>1.0-SNAPSHOT</version>
        <scope>test</scope>
      </dependency>

      <dependency>
        <groupId>dev.sarek</groupId>
        <artifactId>sarek-special</artifactId>
        <version>1.0-SNAPSHOT</version>
        <scope>test</scope>
      </dependency>
      <dependency>
        <groupId>dev.sarek</groupId>
        <artifactId>sarek-junit4-runner</artifactId>
        <version>1.0-SNAPSHOT</version>
        <scope>test</scope>
      </dependency>
      <dependency>
        <groupId>dev.sarek</groupId>
        <artifactId>sarek-spock-extension</artifactId>
        <version>1.0-SNAPSHOT</version>
        <scope>test</scope>
      </dependency>
      <dependency>
        <groupId>dev.sarek</groupId>
        <artifactId>sarek-junit5-extension</artifactId>
        <version>1.0-SNAPSHOT</version>
        <scope>test</scope>
      </dependency>
      <dependency>
        <groupId>net.bytebuddy</groupId>
        <artifactId>byte-buddy</artifactId>
        <version>${bytebuddy.version}</version>
      </dependency>
      <dependency>
        <groupId>net.bytebuddy</groupId>
        <artifactId>byte-buddy-agent</artifactId>
        <version>${bytebuddy.version}</version>
      </dependency>

      <dependency>
        <groupId>de.scrum-master.spock</groupId>
        <artifactId>instrument-jre-classes</artifactId>
        <version>1.0-SNAPSHOT</version>
        <scope>test</scope>
      </dependency>

    </dependencies>
  </dependencyManagement>

  <modules>
    <module>instrument-jre-classes</module>
    <module>perform-tests</module>
    <module>kotlin-sample</module>
  </modules>

  <!--
    Caveat: Automatic, JDK-based profile activation can *not* be inherited by child POMs defining
    the same profiles. Thus, we have to repeat activation conditions there.

    Note: We can check if automatic profile activation works via mvn help:active-profiles.
  -->
  <profiles>
    <profile>
      <id>jdk-8</id>
      <activation>
        <jdk>[1.8,1.9)</jdk>
      </activation>
    </profile>
    <profile>
      <id>jdk-9</id>
      <activation>
        <jdk>[1.9,)</jdk>
      </activation>
    </profile>
    <profile>
      <id>jdk-16-to-xx</id>
      <activation>
        <jdk>[16,)</jdk>
      </activation>
    </profile>
  </profiles>

</project>