* -viper-config can be used to set also the options defined by command line flags
   * the default config file is "e2e.yaml/toml/json/..." and the test starts when no such config is found (as before) but if -viper-config is used, the config file must exist
   * -viper-config can be used to select a file with full path, with or without file suffix

  public void testAssignableClassToClass() {
    @SuppressWarnings("rawtypes") // To test TypeToken<List>
    TypeToken<List> tokL = new TypeToken<List>() {};
    assertTrue(tokL.isSupertypeOf(List.class));
    assertTrue(tokL.isSupertypeOf(ArrayList.class));
    assertFalse(tokL.isSupertypeOf(List[].class));

    TypeToken<Number> tokN = new TypeToken<Number>() {};
    assertTrue(tokN.isSupertypeOf(Number.class));

				"application/vnd.groove-account",
				"application/vnd.groove-help",
				"application/vnd.groove-identity-message",
				"application/vnd.groove-injector",
				"application/vnd.groove-tool-message",
				"application/vnd.groove-tool-template",
				"application/vnd.groove-vcard",
				"application/vnd.handheld-entertainment+xml",
				"application/vnd.hbci",
				"application/vnd.hcl-bireports",
				"application/vnd.hhe.lesson-player",

- **Java Version**: 17+
- **Dependencies**:
  - Apache Commons IO 2.19.0 (runtime)
  - JUnit 4.13.2 (test)
- **Module Name**: `org.codelibs.curl4j`
- **Package Structure**: `org.codelibs.curl.*`
- **Build Tool**: Maven 3.x
- **Test Coverage**: JaCoCo plugin enabled

## Code Style

- Uses external Eclipse formatter configuration from CodeLibs
- Apache License 2.0 headers on all source files (updated to 2025)

   * analysis that that means "plain {@code T}" rather than the inferred type {@code @Nullable T}.
   * (And even if annotations on local variables were permitted as an optional hint, no annotation
   * would be the right tool for the job here: {@code @Nullable} is the annotation that we're trying
   * to get rid of, and {@code @NonNull} would be wrong for our use case for the same reason as

   * analysis that that means "plain {@code T}" rather than the inferred type {@code @Nullable T}.
   * (And even if annotations on local variables were permitted as an optional hint, no annotation
   * would be the right tool for the job here: {@code @Nullable} is the annotation that we're trying
   * to get rid of, and {@code @NonNull} would be wrong for our use case for the same reason as

   *
   * Note that OkHttp's runtime version may be different from the version specified in your
   * project's build file due to the dependency resolution features of your build tool.
   *
   * [semver]: https://semver.org
   */
  val VERSION: String

#dee2e6;\n}\n\n.card-primary.card-outline-tabs > .card-header a.active,\n.card-primary.card-outline-tabs > .card-header a.active:hover {\n  border-top: 3px solid #007bff;\n}\n\n.bg-primary > .card-header .btn-tool,\n.bg-gradient-primary > .card-header .btn-tool,\n.card-primary:not(.card-outline) > .card-header .btn-tool {\n  color: rgba(255, 255, 255, 0.8);\n}\n\n.bg-primary > .card-header .btn-tool:hover,\n.bg-gradient-primary > .card-header .btn-tool:hover,\n.card-primary:not(.card-outline) > .card-header .btn-tool:hover...

   * analysis that that means "plain {@code T}" rather than the inferred type {@code @Nullable T}.
   * (And even if annotations on local variables were permitted as an optional hint, no annotation
   * would be the right tool for the job here: {@code @Nullable} is the annotation that we're trying
   * to get rid of, and {@code @NonNull} would be wrong for our use case for the same reason as

   * analysis that that means "plain {@code T}" rather than the inferred type {@code @Nullable T}.
   * (And even if annotations on local variables were permitted as an optional hint, no annotation
   * would be the right tool for the job here: {@code @Nullable} is the annotation that we're trying
   * to get rid of, and {@code @NonNull} would be wrong for our use case for the same reason as