SimpleProblemCollector result = validateRaw("duplicate-plugin-execution.xml");

        assertViolations(result, 0, 4, 0);

        assertContains(result.getErrors().get(0), "duplicate execution with id a");
        assertContains(result.getErrors().get(1), "duplicate execution with id default");
        assertContains(result.getErrors().get(2), "duplicate execution with id c");

    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();
    }

# 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

└── fess-crawler-opensearch/  # OpenSearch backend
```

### Key Components

#### Core Engine
- **Crawler**: Main orchestrator managing crawl execution
- **CrawlerContext**: Execution context and configuration
- **CrawlerThread**: Individual crawler thread implementation

#### Client Architecture
- **HcHttpClient**: HTTP/HTTPS client using Apache HttpComponents

// TODO(b/154564140): Move this to its own header. This requires splitting
// c_api_experimental.h
struct TFE_ContextOptions {
  TF_SessionOptions session_options;
  // true if async execution is enabled.
  bool async = false;
  TFE_ContextDevicePlacementPolicy device_placement_policy{
      TFE_DEVICE_PLACEMENT_SILENT};
  // If true, use TFRT backend
  bool use_tfrt = false;

            // first one is known, so it comes first
            return -1;
        }
        int rv = Integer.compare(i1, i2);
        if (rv != 0) {
            return rv;
        }
        // same execution point, now compare priorities
        return Integer.compare(p1.priority(), p2.priority());
    }

     * from the runtime environment like {@link System#getProperties()} and environment variables.
     *
     * @return The execution properties, never {@code null}.
     */
    Map<String, String> getSystemProperties();

    /**
     * Gets the user properties to use for interpolation and profile activation. The user properties have been

 * Built-in scopes include:
 * <ul>
 *   <li>{@link Singleton} - One instance per container</li>
 *   <li>{@link SessionScoped} - One instance per Maven session</li>
 *   <li>{@link MojoExecutionScoped} - One instance per plugin execution</li>
 * </ul>
 *
 * @see Singleton
 * @see SessionScoped
 * @see MojoExecutionScoped
 * @since 4.0.0
 */
@Target(ANNOTATION_TYPE)
@Retention(RUNTIME)
@Documented

 *
 * This class ensures that at most one thread is running at a time. This is initially the JUnit test
 * thread, which yields its execution privilege while calling [runTasks], [runNextTask], or
 * [advanceUntil]. These functions don't return until the task threads are all idle.
 *
 * Task threads release their execution privilege in these ways:
 *
 *  * By yielding in [TaskRunner.Backend.coordinatorWait].
 *  * By yielding in [BlockingQueue.poll].

            Defines a default phase to bind a Mojo execution to if the user does not explicitly set a phase in the POM.
            <p><b>Note:</b> This will not automagically make a Mojo run when the plugin declaration is added
            to the POM. It merely enables the user to omit the {@code <phase>} element from the
            surrounding {@code <execution>} element.</p>
          </description>
        </field>