<artifactId>maven-it-plugin-log-file</artifactId>
          <version>2.1-SNAPSHOT</version>
        </plugin>
      </plugins>
    </pluginManagement>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>
        <configuration>
          <logFile>target/exec.log</logFile>
          <string>exec</string>

      <snapshots/>
      <releases/>
    </repository>
  </repositories>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <id>equal-build-exec-id</id>
            <phase>initialize</phase>
            <goals/>

      <!-- NOTE: It's essential part of this test variant to redefine the test plugin again, i.e. trigger plugin merging -->
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
      </plugin>
    </plugins>
  </build>

        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <id>inherited-execution</id>
            <inherited>true</inherited>
            <phase>validate</phase>
            <goals>
              <goal>log-string</goal>
            </goals>
            <configuration>

		<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>

              [INFO]    Ignored 53 units with compilation errors in first pass.
              [INFO] Compile with -strict or with -logLevel set to TRACE or DEBUG to see all errors.

            Turning up the log level, we see that GWT is trying to compile classes from other
            packages, like RangeTest. The reason for this is that GWT doesn't distinguish between

        <artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <id>equal-build-exec-id</id>
            <phase>initialize</phase>
            <goals>
              <goal>reset</goal>
            </goals>
            <configuration>
              <logFile>target/exec.log</logFile>
              <string>test</string>

    in the default lifecycle bindings for the project's packaging.
  </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>
        <!-- NOTE: It's essential that this plugin is also referenced by the default lifecycle bindings -->

        <version>2.1-SNAPSHOT</version>
      </plugin>
      <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>

            <version>2.1-SNAPSHOT</version>
          </plugin>
          <plugin>
            <groupId>org.apache.maven.its.plugins</groupId>
            <artifactId>maven-it-plugin-log-file</artifactId>
            <version>2.1-SNAPSHOT</version>
            <configuration>
              <logFile>target/it.properties</logFile>
            </configuration>
            <executions>
              <execution>