assertEquals(
                "1 problem was encountered while building the effective toolchains" + LS
                        + "[ERROR] MESSAGE @ line 3, column 5" + LS,
                e.getMessage());
    }

    @Test
    void testUnknownPositionAndSource() {
        ProblemCollector problemCollector = ProblemCollectorFactory.newInstance(null);

 * property {@code maven.ext.class.path} on the command line. As soon as dependency injection is set up, Maven
 * looks up all implementers of this interface and calls their {@link #init(Context)} method. Note:
 * Implementors are strongly advised to inherit from {@link AbstractEventSpy} instead of directly implementing this
 * interface.
 * @since 3.0.2
 */
public interface EventSpy {

                }
            }
        } catch (IOException | XMLStreamException e) {
            // The root locator can be used very early during the setup of Maven,
            // even before the arguments from the command line are parsed.  Any exception
            // that would happen here should cause the build to fail at a later stage
            // (when actually parsing the POM) and will lead to a better exception being

    public SettingsConfigurationException(String message, Throwable cause, int lineNumber, int columnNumber) {
        super(
                message
                        + (lineNumber > 0 ? System.lineSeparator() + "  Line:   " + lineNumber : "")
                        + (columnNumber > 0 ? System.lineSeparator() + "  Column: " + columnNumber : ""),
                cause);
        this.lineNumber = lineNumber;

 *
 * mavenBuild("<jdk>", "<profiles> <goals> <plugins> <properties>"
 *
 * @param jdk the jdk tool name (in jenkins) to use for this build
 * @param extraArgs extra command line args
 */
def mavenBuild(jdk, extraArgs) {
  script {
    try {
      withEnv(["JAVA_HOME=${tool "$jdk"}",
               "PATH+MAVEN=${tool "$jdk"}/bin:${tool "maven_3_latest"}/bin",

   per project settings can be defined by files in <<<.mvn/>>> directory:

   * <<<.mvn/jvm.config>>> containing jvm options,

   * <<<.mvn/maven.config>>> containing Maven command-line parameter,

   * <<<.mvn/extensions.xml>>> containing {{{./core-extensions.html}a list of extensions}},

 * since 3.5.0, output is colorized by default, with color disabled in batch mode: see

 */
package org.apache.maven.lifecycle.internal;

import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;

/**
 * Describes the required task segment as provided on the maven command line; i.e. "clean jetty:run install"
 *
 * <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 {

    /**
     * Main method to start the Fess application.
     * Sets up system properties, configures Tomcat, and starts the server.
     *
     * @param args command line arguments (not used)
     */
    public static void main(final String[] args) {
        // update java.io.tmpdir
        final String tempPath = System.getProperty(FESS_TEMP_PATH);
        if (tempPath != null) {

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

/**
 * Defines the contract for parsing Maven command-line arguments and creating an execution or invoker requests.
 *
 * @since 4.0.0
 */
@Experimental
public interface Parser {
    /**
     * Parses the given ParserRequest to create an {@link InvokerRequest}.
     * This method does interpret tool arguments.
     *

 -----
 Introduction
 -----
 Hervé Boutemy
 -----
 2025-11-16
 -----

Maven 4 API - CLI

 This is the {{{./apidocs/org/apache/maven/api/cli/package-summary.html}API}} for Maven's command-line interface and
 tools:

   * <<<{{{./apidocs/org/apache/maven/api/cli/mvn/package-summary.html}mvn}}>>>, the Maven build tool,