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

/**
 * Dependency scope.
 * This represents at which time the dependency will be used, for example, at compile time only,
 * at run time or at test time.  For a given dependency, the scope is directly derived from the
 * {@link org.apache.maven.api.model.Dependency#getScope()} and will be used when using {@link PathScope}

  cannot succeed; no artifact downloads can take place, regardless of whether
  they are snapshot versions; artifact deployment cannot take place; certain
  types of tests cannot be setup, since the container used to run them cannot be
  reached or started.

  All of these operations will produce their own unique errors in the absence of
  a coordinated offline strategy. In addition, efforts to unite these failing

                    LOGGER.warn(
                            "File '{}' is more recent than the packaged artifact for '{}', "
                                    + "please run a full `mvn package` build",
                            relativizeOutputFile(outputFile),
                            project.getArtifactId());
                    return true;
                }
            }

Quick Build
-------
If you want to bootstrap Maven, you'll need:
- Java 17+
- Maven 3.6.3 or later
- Run Maven, specifying a location into which the completed Maven distro should be installed:
    ```
    mvn -DdistributionTargetDir="$HOME/app/maven/apache-maven-4.0.x-SNAPSHOT" clean package
    ```

 *
 * <strong>NOTE:</strong> This class is not part of any public api and can be changed or deleted without prior notice.
 *
 * @since 3.0
 */
public final class TaskSegment {

    // Can be both "LifeCycleTask" (clean/install) and "GoalTask" (org.mortbay.jetty:maven-jetty-plugin:6.1.19:run)

    private final List<Task> tasks;

    if match is found, the toolchain instance is made available to other Maven plugins.</p>
    <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use
    the same other JDK instance without hardcoding absolute paths into the {@code pom.xml}
    and without configuring every plugin that require path to JDK tools.</p>

org.codehaus.plexus.util.cli; public synchronized class StreamFeeder extends Thread { private java.io.InputStream input; private java.io.OutputStream output; private boolean done; public void StreamFeeder(java.io.InputStream, java.io.OutputStream); public void run(); public void close(); public boolean isDone(); private void feed() throws java.io.IOException; } org/codehaus/plexus/util/cli/StreamPumper.class package org.codehaus.plexus.util.cli; public synchronized class StreamPumper extends Thread { private...

 files.

 For many of the more advanced features in Maven2 it is critical that POMs be available in the local repository.
 Features like transitive dependencies and the new parent specification mechanism. The problem we run into is
 that currently we have information about a project scattered across the project.xml and the
 various properties files. What needs to be done is to encapsulate all of this in the POM.

          </association>
        </field>
        <field>
          <name>configuration</name>
          <version>1.0.0</version>
          <type>DOM</type>
          <description>Configuration to pass to all goals run in this phase.</description>
        </field>
      </fields>
    </class>
    <class>
      <name>Execution</name>
      <version>1.0.0</version>
      <description>A set of goals to execute.</description>

        assertEquals(1, ((List<?>) pom.getValue("reporting/plugins[1]/reportSets[1]/reports")).size());
        assertEquals("run", pom.getValue("reporting/plugins[1]/reportSets[1]/reports[1]"));
    }

    /* MNG-2309*/
    @Test
    void testProfileInjectionOrder() throws Exception {