*   <li>{@link Tables}
 * </ul>
 *
 * <h2>Abstract implementations</h2>
 *
 * <ul>
 *   <li>{@link AbstractIterator}
 *   <li>{@link AbstractSequentialIterator}
 *   <li>{@link UnmodifiableIterator}
 *   <li>{@link UnmodifiableListIterator}
 * </ul>
 *
 * <h2>Forwarding collections</h2>
 *
 * We provide implementations of collections that forward all method calls to a delegate collection

    }

    /**
     * Test multiple FileInformation implementations can coexist
     */
    @Test
    @DisplayName("Test multiple FileInformation implementations")
    void testMultipleFileInformationImplementations() {
        // Create different mock implementations
        FileInformation basicInfo = mock(FileInformation.class);

 * [system DNS service][SYSTEM], which is the default. Some applications may provide their own
 * implementation to use a different DNS server, to prefer IPv6 addresses, to prefer IPv4 addresses,
 * or to force a specific known IP address.
 *
 * Implementations of this interface must be safe for concurrent use.
 */
fun interface Dns {
  /**

  SUPPORTS_REMOVE,
  /**
   * Support for {@link ListIterator#add(Object)}; ignored for plain {@link Iterator}
   * implementations.
   */
  SUPPORTS_ADD,
  /**
   * Support for {@link ListIterator#set(Object)}; ignored for plain {@link Iterator}
   * implementations.
   */
  SUPPORTS_SET;

  /**
   * A set containing none of the optional features of the {@link Iterator} or {@link ListIterator}
   * interfaces.
   */

# Extractor Implementation Tests

This directory contains comprehensive tests for the Extractor implementations, focusing on the improvements made to resource management, error handling, and input validation.

## Test Files Overview

### 1. ExtractorResourceManagementTest.java
**Purpose**: Verify proper resource management in Extractor implementations.

**Key Test Areas**:
- Resource closure on successful extraction (MS Office extractors)

import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Provides a unique identifier for dependencies when multiple implementations
 * of the same type are available.
 * <p>
 * This annotation can be used in conjunction with {@link Inject} to specify
 * which implementation should be injected when multiple candidates exist.
 * The value represents a unique identifier for the dependency.
 * <p>
 * Example usage:

 * override {@code addAll} as well, either providing your own implementation, or delegating to the
 * provided {@code standardAddAll} method.
 *
 * <p><b>{@code default} method warning:</b> This class does <i>not</i> forward calls to {@code
 * default} methods. Instead, it inherits their default implementations. When those implementations
 * invoke methods, they invoke methods on the {@code ForwardingSortedSet}.
 *

import org.apache.maven.api.di.Named;

/**
 * Service provider interface for registering custom {@link Packaging} implementations.
 * <p>
 * This interface allows plugins and extensions to define and register additional packaging types
 * beyond the standard ones provided by Maven (like jar, war, ear, etc.). Implementations of this
 * interface will be discovered through the Java ServiceLoader mechanism and their provided

/**
 * Service provider interface for registering custom {@link Lifecycle} implementations.
 * <p>
 * This interface allows plugins and extensions to define and register additional build lifecycles
 * beyond the standard ones provided by Maven (like clean, default, site). Lifecycles define a sequence
 * of phases that can be executed during a build.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism

/**
 * Service provider interface for registering custom {@link PathScope} implementations.
 * <p>
 * This interface allows plugins and extensions to define and register additional path scopes
 * beyond the standard ones provided by Maven. Path scopes define how dependencies are used
 * in different contexts, such as compilation, testing, or runtime.
 * <p>
 * Implementations of this interface will be discovered through the Java ServiceLoader mechanism