</goals>
            <phase>generate-sources</phase>
            <configuration>
              <version>1.3.0</version>
              <templates>
                <template>model-v3.vm</template>
              </templates>
            </configuration>
          </execution>
          <execution>
            <id>modello-site-docs</id>
            <phase>none</phase>
          </execution>

        for (String task : tasks) {
            if (isBeforeOrAfterPhase(task)) {
                String prevTask = task;
                task = PhaseId.of(task).phase();
                logger.warn("Illegal call to phase '{}'. The main phase '{}' will be used instead.", prevTask, task);
            }
            if (isGoalSpecification(task)) {

            if (lastLifecyclePhase == null) {
                lastLifecyclePhase = phaseId.phase();
            } else if (!phaseId.phase().equals(lastLifecyclePhase)) {
                project.addLifecyclePhase(lastLifecyclePhase);
                lastLifecyclePhase = phaseId.phase();
            }
        }

        if (lastLifecyclePhase != null) {

            <id>compile</id>
            <phase>initialize</phase>
            <goals>
              <goal>set</goal>
            </goals>
            <configuration>
              <mainFile>dependency-classes</mainFile>
            </configuration>
          </execution>
          <execution>
            <id>install</id>
            <phase>generate-sources</phase>
            <goals>
              <goal>set</goal>

    volatile Exception exception;

    public BuildStep(String name, MavenProject project, Lifecycle.Phase phase) {
        this.name = Objects.requireNonNull(name, "name cannot be null");
        this.project = Objects.requireNonNull(project, "project cannot be null");
        this.phase = phase;
    }

    public boolean isCreated() {
        return status.get() == CREATED;
    }

 * followed by <dfn>flattening</dfn> and <dfn>resolution</dfn>.
 * The version selection is done for each dependency during the collection phase.
 * The flatten phase keeps only a single version per ({@code groupId}, {@code artifactId}) pair.
 * The resolution phase actually downloads the dependencies (or artifacts) that have been computed.
 *
 * @since 4.0.0
 */
@Experimental
@Immutable

 *   </tr>
 *   <tr>
 *      <td>execute</td>
 *      <td>@Execute
 *       ( phase=LifecyclePhase.&lt;phase&gt;, goal= "&lt;goal-name&gt;", lifecycle="&lt;lifecycle-id&gt;" )</td>
 *      <td>No</td>
 *      <td>When this goal is invoked, it will first invoke a parallel lifecycle, ending at the given phase.
 *          If a goal is provided instead of a phase, that goal will be executed in isolation.

        <artifactId>maven-dependency-plugin</artifactId>
        <version>3.2.0</version>
        <executions>
          <execution>
            <id>copy-model</id>
            <phase>generate-sources</phase>
            <goals>
              <goal>copy</goal>
            </goals>
            <configuration>
              <artifactItems>
                <artifactItem>

        <artifactId>maven-bundle-plugin</artifactId>
        <version>${maven-bundle-plugin.version}</version>
        <executions>
          <execution>
            <id>bundle-manifest</id>
            <phase>process-classes</phase>
            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <instructions>

            <id>test</id>

            <!--  The key to this test... -->
            <inherited>false</inherited>

            <goals>
              <goal>compile</goal>
            </goals>
            <phase>install</phase>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>