import org.apache.maven.api.model.PluginContainer;

/**
 * Represents the packaging of a Maven project.
 *
 * <p>The {@code Packaging} class defines the type of artifact that a Maven project produces during the build process.
 * The packaging type determines the structure of the project's output and how Maven will treat the resulting artifact.</p>
 *

# 使用覆盖测试依赖项 { #testing-dependencies-with-overrides }

## 测试时覆盖依赖项 { #overriding-dependencies-during-testing }

有些场景下，您可能需要在测试时覆盖依赖项。

即不希望运行原有依赖项（及其子依赖项）。

反之，要在测试期间（或只是为某些特定测试）提供只用于测试的依赖项，并使用此依赖项的值替换原有依赖项的值。

### 用例：外部服务 { #use-cases-external-service }

常见实例是调用外部第三方身份验证应用。

向第三方应用发送令牌，然后返回经验证的用户。

但第三方服务商处理每次请求都可能会收费，并且耗时通常也比调用写死的模拟测试用户更长。

一般只要测试一次外部验证应用就够了，不必每次测试都去调用。

此时，最好覆盖调用外部验证应用的依赖项，使用返回模拟测试用户的自定义依赖项就可以了。

# 用覆寫測試相依 { #testing-dependencies-with-overrides }

## 在測試期間覆寫相依 { #overriding-dependencies-during-testing }

有些情境你可能想在測試時覆寫（override）某個相依（dependency）。

你不希望執行原本的相依（以及它可能具有的任何子相依）。

相反地，你想提供一個只在測試期間使用的不同相依（可能只在特定測試中），並回傳一個可以在原本相依值被使用之處使用的值。

### 使用情境：外部服務 { #use-cases-external-service }

例如你有一個需要呼叫的外部驗證提供者。

你傳送一個 token，它會回傳一個已驗證的使用者。

這個提供者可能按每個請求收費，而且呼叫它可能比在測試中使用固定的模擬使用者多花一些時間。

你大概只想對外部提供者測試一次，而不需要在每個測試都呼叫它。

                // Ignore listing errors during cleanup
                log.debug("Error listing files during cleanup", e);
            }
        }

        try {
            file.delete();
        } catch (SmbException e) {
            // Ignore deletion errors during cleanup
            log.debug("Error deleting file during cleanup", e);
        }
    }

)

if NOT "%FESS_HEAP_SIZE%" == "" (
set FESS_MIN_MEM=%FESS_HEAP_SIZE%
set FESS_MAX_MEM=%FESS_HEAP_SIZE%
)

REM min and max heap sizes should be set to the same value to avoid
REM stop-the-world GC pauses during resize, and so that we can lock the
REM heap in memory on startup to prevent any of it from being swapped
REM out.
set FESS_JAVA_OPTS=%FESS_JAVA_OPTS% -Xms%FESS_MIN_MEM% -Xmx%FESS_MAX_MEM%

import jakarta.annotation.Resource;

/**
 * Service class for managing request headers used in web crawling configurations.
 * This service provides CRUD operations for request headers that are applied
 * during web crawling to configure HTTP request behavior.
 *
 */
public class RequestHeaderService {

    /**
     * Behavior for request header database operations.
     */
    @Resource

import java.util.concurrent.Executor;
import java.util.concurrent.TimeUnit;
import java.util.concurrent.TimeoutException;

/**
 * Base class for services that do not need a thread while "running" but may need one during startup
 * and shutdown. Subclasses can implement {@link #startUp} and {@link #shutDown} methods, each which
 * run in an executor which by default uses a separate thread for each method.
 *
 * @author Chris Nokleberg

    /**
     * Close all connections and release resources associated with this context
     *
     * @return whether any connection was still in use
     * @throws CIFSException if an error occurs during cleanup
     */
    boolean close() throws CIFSException;

    /**
     * Get the configuration object for this context
     *
     * @return the active configuration
     */
    Configuration getConfig();

            @Override
            public boolean close() throws CIFSException {
                super.close(); // Call original close to set closeCalled
                throw new CIFSException("Test exception during close");
            }
        };

        // Simulate the shutdown hook being run
        spyContext.run();

        assertTrue(spyContext.isCloseCalled()); // Verify close() was called

        // Release the session (back to initial state)
        session.release();
        assertFalse(session.isInUse(), "Session should not be in use after release");
    }

    /**
     * Test exception handling during cleanup
     */
    @Test
    @Timeout(5)
    public void testExceptionHandling() throws Exception {
        SmbSessionImpl session = new SmbSessionImpl(mockContext, "testhost", "testdomain", mockTransport);