}
class Example {
    Property<NestedType> getNestedProperty()
}
```

This is unnecessary because users will have trouble creating instances of `NestedType` and merging different instances of `NestedType`. It's also more awkward for users to access the properties in the nested property.

If the nested type is a managed type (Gradle can generate its implementation), you can define a nested property with:
```
interface NestedType {

  }

  /**
   * Creates an {@code ImmutableMap<String, String>} from a {@code Properties} instance. Properties
   * normally derive from {@code Map<Object, Object>}, but they typically contain strings, which is
   * awkward. This method lets you get a plain-old-{@code Map} out of a {@code Properties}.
   *
   * @param properties a {@code Properties} object to be converted

  }

  /**
   * Creates an {@code ImmutableMap<String, String>} from a {@code Properties} instance. Properties
   * normally derive from {@code Map<Object, Object>}, but they typically contain strings, which is
   * awkward. This method lets you get a plain-old-{@code Map} out of a {@code Properties}.
   *
   * @param properties a {@code Properties} object to be converted

  }

  public void testFrom() {
    Function<String, Integer> forward = Integer::parseInt;
    Function<Object, String> backward = toStringFunction();

    Converter<String, Number> converter = Converter.<String, Number>from(forward, backward);

    assertThat(converter.convert(null)).isNull();
    assertThat(converter.reverse().convert(null)).isNull();

        .containsExactly(Country.CANADA, Country.SWITZERLAND, Country.CHILE)
        .inOrder();
    // backward map ordered by country
    assertThat(bimap.inverse().keySet())
        .containsExactly(Country.CANADA, Country.CHILE, Country.SWITZERLAND)
        .inOrder();
    // backward map ordered by country (even for currency values)
    assertThat(bimap.inverse().values())

### Migration and Enforcement

* **New code**: All new contributions must use American English
* **Existing code**: British English spellings in existing code should be updated opportunistically when those areas are modified, unless constrained by backward compatibility

	<component name="pingJob" class="org.codelibs.fess.job.PingSearchEngineJob" instance="prototype">
	</component>
	<component name="pythonJob" class="org.codelibs.fess.job.PythonJob" instance="prototype">
	</component>
	<!-- Backward Compatibility  -->
	<component name="pingEsJob" class="org.codelibs.fess.job.PingSearchEngineJob" instance="prototype">
	</component>

        assertNull(ssoManager.getResponse(SsoResponseType.METADATA));
        assertNull(ssoManager.getResponse(SsoResponseType.LOGOUT));
        assertNull(ssoManager.logout(FessUserBean.empty()));
    }

    // Test backward compatibility: aad -> entraid mapping
    @Test
    public void test_getAuthenticator_aadMapsToEntraid() {
        // Register an authenticator with the new "entraid" name

        assertEquals(error, exception.getCause());
    }

    @Test
    public void test_constructorWithThrowableCause_BackwardCompatibility() {
        // Verify backward compatibility with Exception parameter
        String message = "SSO login failed";

        // Test with various Exception types
        IOException ioException = new IOException("Connection failed");

    }

    @Override
    protected String getValidationError() {
        return null;
    }

    // ============================================================
    // Deprecated delegate methods for backward compatibility
    // ============================================================

    /**
     * Builds the query for suggestions.
     * @param q The query string.
     * @param fieldList The fields to search in.