* MNG-6300: resolvedArtifacts can be cache result; this ensures reactor files are always up-to-date
                 * During lifecycle the Artifact.getFile() can change from target/classes to the actual jar.
                 * This clearly shows that target/classes should not be abused as artifactFile just for the classpath
                 */
                File reactorProjectFile = reactorProjects.get(artifact);

en-plugin-api\src\main\java src/main/scripts c:\home\Brett\cvs\maven-2\maven-components-release\maven-plugin-api\src\test\java c:\home\Brett\cvs\maven-2\maven-components-release\maven-plugin-api\target\classes c:\home\Brett\cvs\maven-2\maven-components-release\maven-plugin-api\target\test-classes c:\home\Brett\cvs\maven-2\maven-components-release\maven-plugin-api\src\main\resources c:\home\Brett\cvs\maven-2\maven-components-release\maven-plugin-api\src\test\resources c:\home\Brett\cvs\maven-2\ma...

    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for
    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages
    have prod supersource, even if they have none. GWT is happy to ignore us

        }
    }

    @Nested
    @DisplayName("Inheritance verification")
    class InheritanceVerification {

        @Test
        @DisplayName("should properly extend base classes")
        void testInheritance() {
            // Arrange
            SamrPolicyHandle ph = createMockPolicyHandle();

            // Act

- DI via `@Resource` annotation
- `HtmlResponse` for JSP, `JsonResponse` for APIs

### Services
- Business logic in `app.service.*`
- Injected into Actions
- Use behavior classes to access OpenSearch

### Helpers
- Cross-cutting utilities in `helper.*`
- Stateless, injected via DI
- Access via `ComponentUtil.getFooHelper()`

## Development Notes

import com.google.common.annotations.GwtCompatible;
import java.util.concurrent.Future;
import org.jspecify.annotations.NullUnmarked;
import org.jspecify.annotations.Nullable;

/**
 * Classes and futures used in {@link FuturesGetCheckedTest} and {@link FuturesGetUncheckedTest}.
 */
@GwtCompatible
@NullUnmarked
final class FuturesGetCheckedInputs {

                  ListFeature.SUPPORTS_SET)
              .createTestSuite());
    }
    return suite;
  }

  // Test generators.  To let the GWT test suite generator access them, they need to be
  // public named classes with a public default constructor.

  public static final class DoublesAsListGenerator extends TestDoubleListGenerator {
    @Override
    protected List<Double> create(Double[] elements) {
      return asList(elements);

    assertSame(EXCEPTION, record.getThrown());
  }

  public void testConcurrentModification() throws Exception {
    // Tests for the absence of a bug where logging while iterating over the
    // stored log records causes a ConcurrentModificationException
    assertTrue(handler.getStoredLogRecords().isEmpty());
    ExampleClassUnderTest.foo();
    ExampleClassUnderTest.foo();
    for (LogRecord unused : handler.getStoredLogRecords()) {

- ZipExtractor: 6 tests
- TarExtractor: 6 tests

## Running the Tests

### Run all extractor tests:
```bash
mvn test -Dtest=Extractor*Test
```

### Run specific test classes:
```bash
mvn test -Dtest=ExtractorResourceManagementTest
mvn test -Dtest=AbstractExtractorTest
mvn test -Dtest=ArchiveExtractorErrorHandlingTest
```

### Run tests for specific extractor:
```bash

# Custom Request and APIRoute class { #custom-request-and-apiroute-class }

In some cases, you may want to override the logic used by the `Request` and `APIRoute` classes.

In particular, this may be a good alternative to logic in a middleware.

For example, if you want to read or manipulate the request body before it is processed by your application.

/// danger

This is an "advanced" feature.