private final List<ScoreBooster> scoreBoosterList = new ArrayList<>();

    /**
     * Executes all score boosters.
     * @return The result of the execution.
     */
    public String execute() {
        final StringBuilder resultBuf = new StringBuilder();
        scoreBoosterList.forEach(b -> {
            try {
                final long count = b.process();

# END TF TEST SUITE OPTIONS

# START CROSS-COMPILE CONFIGS
# Set execution platform to Linux x86
# Note: Lot of the "host_" flags such as "host_cpu" and "host_crosstool_top"
# flags seem to be actually used to specify the execution platform details. It
# seems it is this way because these flags are old and predate the distinction
# between host and execution platform.
common:cross_compile_base --config=clang_local

    private final String projectId;

    public ProjectBuildFailureException(String projectId, MojoFailureException cause) {
        super("Build for project: " + projectId + " failed during execution of mojo.", cause);

        this.projectId = projectId;
    }

    public MojoFailureException getMojoFailureException() {
        return (MojoFailureException) getCause();
    }

 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.execution;

import java.util.List;

import org.apache.maven.project.MavenProject;
import org.junit.jupiter.api.Test;

import static org.junit.jupiter.api.Assertions.assertNotNull;

/**
 * Denotes that a bean should be created as a singleton instance.
 * <p>
 * Singleton-scoped beans are instantiated once and reused throughout the entire
 * Maven execution. This scope should be used for stateless services or components
 * that can be safely shared across the entire build process.
 * <p>
 * Example usage:
 * <pre>
 * {@literal @}Singleton

- plugin artifact retrieval problem
- plugin dependency metadata missing
- plugin dependency metadata retrieval problem
- plugin configuration problem
- plugin execution failure due to something that is known to possibly go wrong (like compilation failure)
- plugin execution error due to something that is not expected to go wrong (the compiler executable missing)

- Support for query parameters, headers, body (String or stream), compression, SSL configuration, proxies, and timeouts
- Automatic in-memory or on-disk caching of request/response bodies
- Synchronous and asynchronous (callback) execution
- Minimal dependencies (only Apache Commons IO)

## Installation

### Maven

Add the dependency to your `pom.xml` (replace `x.y.z` with the latest version):

```xml
<dependency>

    }

    /**
     * Executes the document purging job.
     * Removes all documents from the search index that have expired based on their expires field.
     *
     * @return a string containing the execution result and any error messages
     */
    public String execute() {
        final SearchEngineClient searchEngineClient = ComponentUtil.getSearchEngineClient();

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.graph;

import java.util.List;

import org.apache.maven.execution.ProjectDependencyGraph;
import org.apache.maven.project.MavenProject;
import org.junit.jupiter.api.extension.ExtendWith;
import org.junit.jupiter.params.ParameterizedTest;
import org.junit.jupiter.params.provider.ValueSource;

import org.apache.maven.artifact.resolver.ArtifactResolutionException;
import org.apache.maven.artifact.versioning.InvalidVersionSpecificationException;
import org.apache.maven.execution.MavenSession;
import org.apache.maven.model.Plugin;
import org.apache.maven.plugin.InvalidPluginDescriptorException;
import org.apache.maven.plugin.InvalidPluginException;
import org.apache.maven.plugin.LegacySupport;