<packaging.fess.var.dir>/var/lib/fess</packaging.fess.var.dir>
		<packaging.fess.lib.dir>${packaging.fess.home.dir}/lib</packaging.fess.lib.dir>
		<packaging.fess.log.dir>/var/log/fess</packaging.fess.log.dir>
		<packaging.fess.temp.dir>/var/tmp/fess</packaging.fess.temp.dir>
		<packaging.fess.extension.dir>${packaging.fess.home.dir}/extension</packaging.fess.extension.dir>

        <artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
        <configuration>
          <logFile>target/exec.log</logFile>
          <string>exec</string>
        </configuration>
        <executions>
          <execution>
            <id>exec-1</id>
            <phase>validate</phase>
            <goals>
              <goal>log-string</goal>
            </goals>

    Test the reports are executed in the order given in the POM.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
      </plugin>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-expression</artifactId>

        </plugin>
        <plugin>
          <!-- this checks handling of a plugin which is explicitly bound to the lifecycle -->
          <groupId>org.apache.maven.its.plugins</groupId>
          <artifactId>maven-it-plugin-log-file</artifactId>
          <version>2.1-SNAPSHOT</version>
          <configuration>
            <logFile>passed.txt</logFile>
          </configuration>
        </plugin>
      </plugins>
    </pluginManagement>

            the add-opens. Right now that doesn't seem worth the effort, though.
        -->
        <test.add.opens>
          --add-opens java.base/java.lang=ALL-UNNAMED
          --add-opens java.base/java.util=ALL-UNNAMED
          --add-opens java.base/sun.security.jca=ALL-UNNAMED
        </test.add.opens>
      </properties>
    </profile>
    <profile>