*   </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.

 * 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

## Next Steps

1. **Immediate Actions**:
   - Set up Windows Server test environment
   - Create detailed technical specifications for Phase 1
   - Identify and evaluate Java RDMA libraries

2. **Phase 1 Kickoff**:
   - Begin SMB3 lease implementation
   - Create comprehensive test suite
   - Document API changes

3. **Community Engagement**:
   - Announce implementation plan

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

            <id>modello-plugin</id>
            <goals>
              <goal>velocity</goal>
              <goal>xdoc</goal>
              <goal>xsd</goal>
            </goals>
            <phase>generate-sources</phase>
            <configuration>
              <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
              <version>2.0.0</version>
              <models>

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

import org.apache.maven.project.MavenProject;

/**
 * Lifecycle mapping delegate component interface. Calculates project build execution plan given {@link Lifecycle} and
 * lifecycle phase. Standard lifecycles use plugin execution {@code <phase>} or mojo default lifecycle phase to
 * calculate the execution plan, but custom lifecycles can use alternative mapping strategies.
 * <p>

      </plugin>
      <plugin>
        <artifactId>maven-source-plugin</artifactId>
        <executions>
          <execution>
            <id>attach-test-sources</id>
            <phase>post-integration-test</phase>
            <goals><goal>test-jar</goal></goals>
          </execution>
        </executions>
      </plugin>
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
      </plugin>

        }

        for (Phase phase : lifecycleOverlay.getPhases()) {
            String phaseId = defaultLifecycles.getLifeCycles().stream()
                    .flatMap(l -> l.getDelegate().aliases().stream())
                    .filter(a -> phase.getId().equals(a.v3Phase()))
                    .findFirst()
                    .map(a -> a.v4Phase())
                    .orElse(phase.getId());

     */
    enum Type {
        PROJECT,
        DEPENDENCIES,
        CHILDREN
    }

    /**
     * The phase name.
     */
    String phase();

    /**
     * The type of this pointer.
     */
    Type type();

    /**
     * The scope for dependencies, only if {@code type() == Type.Dependencies}.
     */
    String scope() default "";