* <p>
 * This interface allows plugins and extensions to define and register additional build lifecycles
 * beyond the standard ones provided by Maven (like clean, default, site). Lifecycles define a sequence
 * of phases that can be executed during a build.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism
 * and their provided lifecycles will be available throughout the Maven build process.

- 1 QA engineer for test infrastructure
- 1 DevOps engineer for CI/CD setup

### Timeline
- **Total Duration**: 6-8 months for all features
- **Phases 1-2**: 2-3 months (High priority)
- **Phases 3-4**: 2 months (Medium priority)
- **Phases 5-6**: 2-3 months (Low priority)

### Infrastructure
- Windows Server test lab
- RDMA-capable test hardware
- Continuous integration environment

                List<String> phases = shellContext.lookup.lookup(LifecycleRegistry.class).stream()
                        .flatMap(Lifecycle::allPhases)
                        .map(Lifecycle.Phase::name)
                        .toList();
                // TODO: add goals dynamically
                List<String> goals = List.of("wrapper:wrapper");
                names = Stream.concat(phases.stream(), goals.stream()).toList();

            MavenOptions options = parseArgs("maven.config", args);
            if (options.goals().isPresent()) {
                // This file can only contain options, not args (goals or phases)
                throw new IllegalArgumentException("Unrecognized entries in maven.config (" + configFile + ") file: "
                        + options.goals().get());
            }
            return options;

            assertTrue(result.success(), "Model upgrade should succeed");
            assertTrue(result.modifiedCount() > 0, "Should have upgraded phases");

            // Verify phases were upgraded
            verifyCleanPluginPhases(document);
            verifyFailsafePluginPhases(document);
            verifySitePluginPhases(document);

 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.chat;

/**
 * Callback interface for receiving notifications about chat processing phases.
 * Used for SSE streaming to notify clients about the current processing state.
 */
public interface ChatPhaseCallback {

    /** Phase name for intent detection */
    String PHASE_INTENT = "intent";

     * Attached artifacts are secondary artifacts produced during the build (e.g., sources jar,
     * javadoc jar, test jars). These artifacts are created and attached during specific
     * lifecycle phases, so the collection contents depend on the build phase when this method
     * is called.
     *
     * @param project the project to get attached artifacts for

 */
package org.apache.maven.api;

import java.util.Optional;

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.annotations.Nonnull;

/**
 * Event sent by maven during various phases of the build process.
 * Such events can be listened to using {@link Listener}s objects
 * registered in the {@link Session}.
 *
 * @since 4.0.0
 */
@Experimental
public interface Event {

    /**

     * present, are appended, to those specified on CLI input, if any.
     */
    Optional<String> atFile();

    /**
     * Returns the list of goals and phases to execute.
     *
     * @return an {@link Optional} containing the list of goals and phases to execute, or empty if not specified
     */
    @Nonnull
    Optional<List<String>> goals();

                        + " <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>."
                        + " Available lifecycle phases are: " + defaultLifeCycles.getLifecyclePhaseList() + ".");
            }

            int degreeOfConcurrency = session.getRequest().getDegreeOfConcurrency();
            if (degreeOfConcurrency > 1) {