/**
     * Error/failure icon.
     */
    ERROR('✗', "[ERROR]"),

    /**
     * Warning icon.
     */
    WARNING('⚠', "[WARNING]"),

    /**
     * Detail/bullet point icon.
     */
    DETAIL('•', "-"),

    /**
     * Action/arrow icon.
     */
    ACTION('→', ">");

    private final char unicodeChar;
    private final String asciiFallback;

 */
public class PhaseId {
    /**
     * Interned {@link PhaseId} instances.
     */
    private static final Map<String, PhaseId> INSTANCES = new WeakHashMap<>();

    /**
     * The execution point of this {@link PhaseId}.
     */
    private final PhaseExecutionPoint executionPoint;

    /**
     * The static phase that this dynamic phase belongs to.
     */
    private final String phase;

    /**

    public static final String PATH = "testmail.dfmail";

    // ===================================================================================
    //                                                                         Entry Point
    //                                                                         ===========
    public static TestmailPostcard droppedInto(Postbox postbox, MPCall<TestmailPostcard> postcardLambda) {

        suggester.createNextIndex();
        Thread.sleep(50);

        // Verify that createNextIndex completed without exceptions
        // The update alias should now point to the new index
        final String updateAlias = suggester.getIndex() + ".update";
        aliasResponse = client.admin().indices().prepareGetAliases(updateAlias).execute().actionGet();

   *     throw.
   */
  @CanIgnoreReturnValue
  static Error sneakyThrow(Throwable t) {
    throw new SneakyThrows<Error>().throwIt(t);
  }

  @SuppressWarnings("unchecked") // not really safe, but that's the point
  private Error throwIt(Throwable t) throws T {
    throw (T) t;
  }

  private SneakyThrows() {}

 * information among plugins, is this more like an extension point - do we need a sort of bus for
 * application data - do we need a dictionary for our applications like Apple does. We could easily
 * hook into this and this is the model we need to follow - how many of our REST services do not map
 * directory to a method in the application interface?
 *
 * - research extension points versus plugins
 *

## Open & import the project

In your IDEA, `File` - `Open`, select `.teamcity/pom.xml`, `import as project`, and you'll have a Maven project.

## Project structure

Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project.

There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.

    // Ascii.equalsIgnoreCase(), but it is a signal that its documentation may need updating as
    // regards edge cases.

    // The Unicode point {@code 00df} is the lowercase form of sharp-S (ß), whose uppercase is "SS".
    assertThat("pa\u00dfword".toUpperCase()).isEqualTo("PASSWORD"); // [*]
    assertFalse("pa\u00dfword".equalsIgnoreCase("PASSWORD")); // [*]

    // Ascii.equalsIgnoreCase(), but it is a signal that its documentation may need updating as
    // regards edge cases.

    // The Unicode point {@code 00df} is the lowercase form of sharp-S (ß), whose uppercase is "SS".
    assertThat("pa\u00dfword".toUpperCase()).isEqualTo("PASSWORD"); // [*]
    assertFalse("pa\u00dfword".equalsIgnoreCase("PASSWORD")); // [*]

/**
 * Allows core extensions to participate in Maven build session lifecycle.
 *
 * All callback methods (will) follow beforeXXX/afterXXX naming pattern to
 * indicate at what lifecycle point it is being called.
 *
 * @see <a href="https://maven.apache.org/examples/maven-3-lifecycle-extensions.html">example</a>
 * @see <a href="https://issues.apache.org/jira/browse/MNG-4224">MNG-4224</a>
 * @since 3.0-alpha-3
 */