However, this means that STS tokens signed previously by root credentials will no longer be valid upon upgrading to the latest version with this change. Please re-generate them as you usually do. Additionally, if site replication is ever removed - the STS tokens will become invalid, regenerate them as you usually do....

   *
   * @deprecated Prefer {@linkplain ExecutionError(Error)} a constructor that accepts a cause: Users
   *     of this class typically expect for instances to have a non-null cause. At the moment, you
   *     can <i>usually</i> still preserve behavior by passing an explicit {@code null} cause. Note,
   *     however, that passing an explicit {@code null} cause prevents anyone from calling {@link

   *
   * @deprecated Prefer {@linkplain ExecutionError(Error)} a constructor that accepts a cause: Users
   *     of this class typically expect for instances to have a non-null cause. At the moment, you
   *     can <i>usually</i> still preserve behavior by passing an explicit {@code null} cause. Note,
   *     however, that passing an explicit {@code null} cause prevents anyone from calling {@link

 * file system (those projects are usually about to be built) or from the local repository
 * (they are usually downloaded during dependency collection). Those projects are loaded
 * from a Project Object Model (POM).</p>
 *
 * <p><dfn>Project Object Model</dfn> or <dfn>POM</dfn> refers to the information describing
 * all the information needed to build or consume a project. Those are usually loaded from

        if (flakyTestStrategy != FlakyTestStrategy.ONLY) {
            // No need to split in FlakyTestQuarantine
            tcParallelTests(splitNumber)
        }

        requirements {
            // Smoke tests is usually heavy and the build time is twice on EC2 agents
            requiresNotEc2Agent()
        }

        applyTestDefaults(
            model,
            this,
            ":smoke-test:$task",

        id(buildTypeId(model) + suffix)
        name = "Smoke Ide Tests$suffix"
        description = "Tests against IDE sync process"

        requirements {
            // These tests are usually heavy and the build time is twice on EC2 agents
            requiresNotEc2Agent()
        }

        applyTestDefaults(
            model = model,
            buildType = this,

     * {@link Parser#parseInvocation(ParserRequest)} this method will return {@code true} and invoker should
     * handle this request as "early failure". In these cases, {@link #options()} usually is absent.
     */
    boolean parsingFailed();

    /**
     * Returns {@code true} if this call happens in "embedded" mode.
     *
     * @see ParserRequest#embedded()
     */

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

/**
 * A version or meta-version of an artifact or a dependency.
 * A meta-version is a version suffixed with the {@code SNAPSHOT} keyword.
 * Versions are usually parsed using the {@link org.apache.maven.api.services.VersionParser} service.
 *
 * @since 4.0.0
 * @see org.apache.maven.api.services.VersionParser#parseVersion(String)
 * @see org.apache.maven.api.Session#parseVersion(String)

                  <div class="well">
                      Merging `release` back to `master` is a regular operation you’re free to do, at any time. Usually, you will see conflicts in `notes.md` or `accepted-public-api-changes.json`.
                      On `master` branch, these two files are usually reset (cleaned up), unless you have special reasons not to do so.
                  </div>
                </div>
                </p>

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

/**
 * Interface used to locate the root directory for a given project.
 *
 * The root locator is usually looked up from the plexus container.
 * One notable exception is the computation of the early {@code session.rootDirectory}
 * property which happens very early.  The implementation used in this case