Since the naming of the properties no longer suggests they are experimental, we want to ensure users are aware if the current property stops having an effect.
Since the underlying feature is incubating, its actual behavior can still change or be removed in the minor releases.

These properties CAN be supplemented with command-line options and they SHOULD follow the shared naming scheme described above.

    }
  },

  /** Java variable naming convention, e.g., "lowerCamel". */
  LOWER_CAMEL(CharMatcher.inRange('A', 'Z'), "") {
    @Override
    String normalizeWord(String word) {
      return firstCharOnlyToUpper(word);
    }

    @Override
    String normalizeFirstWord(String word) {
      return Ascii.toLowerCase(word);
    }
  },

  /** Java and C++ class naming convention, e.g., "UpperCamel". */

    }
  },

  /** Java variable naming convention, e.g., "lowerCamel". */
  LOWER_CAMEL(CharMatcher.inRange('A', 'Z'), "") {
    @Override
    String normalizeWord(String word) {
      return firstCharOnlyToUpper(word);
    }

    @Override
    String normalizeFirstWord(String word) {
      return Ascii.toLowerCase(word);
    }
  },

  /** Java and C++ class naming convention, e.g., "UpperCamel". */

        // Test the specific field naming configuration
        JsonMappingOption option = provider.provideMappingOption();

        // The option should be configured with CAMEL_TO_LOWER_SNAKE
        // Field naming is now provided as OptionalThing
        OptionalThing<JsonFieldNaming> fieldNamingOpt = option.getFieldNaming();
        assertTrue("Field naming should be present", fieldNamingOpt.isPresent());

├── lang/        # Reflection & language utilities
├── log/         # Logging utilities
├── message/     # Message resource handling
├── misc/        # AssertionUtil, Base64Util, etc.
├── naming/      # JNDI naming utilities
├── net/         # Network & URL utilities
├── nio/         # NIO file utilities
├── security/    # Security & MessageDigest utilities
├── sql/         # SQL type utilities

   * the builder as documented on each method (except for the rarely used {@link #setThreadFactory},
   * which does not have an equivalent).
   */
  public ThreadFactoryBuilder() {}

  /**
   * Sets the naming format to use when naming threads ({@link Thread#setName}) which are created
   * with this ThreadFactory.
   *
   * <p><b>Java 21+ users:</b> use {@link Thread.Builder#name(String, long)} instead. Note that

import java.net.CookieHandler

/**
 * A cookie jar that delegates to a [java.net.CookieHandler].
 *
 * This implementation delegates everything to [okhttp3.java.net.cookiejar.JavaNetCookieJar], which
 * conforms to the package-naming limitations of JPMS.
 *
 * Callers should prefer to use [okhttp3.java.net.cookiejar.JavaNetCookieJar] directly.
 */
class JavaNetCookieJar private constructor(
  delegate: okhttp3.java.net.cookiejar.JavaNetCookieJar,

- **Strategy**: Normalizer, ReadingConverter, ContentsParser
- **Deferred/Promise**: Async operations

### Index Alias Strategy

Zero-downtime index updates using dual aliases:

```
Index Naming: {baseIndex}.{timestamp}
Example:      my-suggest.20250123120000

Aliases:
├── Search Alias: {baseIndex}          (read operations)
└── Update Alias: {baseIndex}.update   (write operations)
```

        // Create custom naming convention
        NamingConvention customNamingConvention = new MockNamingConvention() {
            @Override
            public String fromClassNameToComponentName(String className) {
                return super.fromClassNameToComponentName(className);
            }
        };

        // Create PagerCreator with custom naming convention

- **Flexibility and Control:**
Java serialization offers limited control over the serialization process, such as excluding certain fields, customizing naming conventions, and handling complex data structures more gracefully.

- **Security:**
Java serialization poses security risks, especially related to deserialization vulnerabilities.

- **Version Compatibility:**