For any non-trivial change, we need to be able to answer these questions:

* Why is this change done? What's the use case?
* For user-facing features, what will the API look like?
* What test cases should it have? What could go wrong?
* How will it roughly be implemented? We'll happily provide code pointers to save you time.

We may ask you to answer these questions directly in the GitHub issue or (for large changes) in a shared Google Doc.

    font-weight: 700;
    font-style: normal
}

body, input {
    font-family: cash-market,"Helvetica Neue",helvetica,sans-serif;
}

.md-typeset h1, .md-typeset h2, .md-typeset h3, .md-typeset h4 {
    font-family: cash-market,"Helvetica Neue",helvetica,sans-serif;
    line-height: normal;
    font-weight: bold;
}

button.dl {
  font-weight: 300;

# Fess
# ======
errors.login_error = Invalid username or password.
errors.sso_login_error=SSO login process failed.
errors.could_not_find_log_file = Could not find {0}.
errors.failed_to_start_crawl_process = Failed to start a crawl process.
errors.invalid_design_jsp_file_name = Invalid JSP file.
errors.design_jsp_file_does_not_exist = The JSP file does not exist.

# Fess
# ======
errors.login_error = Invalid username or password.
errors.sso_login_error=SSO login process failed.
errors.could_not_find_log_file = Could not find {0}.
errors.failed_to_start_crawl_process = Failed to start a crawl process.
errors.invalid_design_jsp_file_name = Invalid JSP file.
errors.design_jsp_file_does_not_exist = The JSP file does not exist.

    this.loggerName = ownerOfLogger.getName();
  }

  Logger get() {
    /*
     * We use double-checked locking. We could the try racy single-check idiom, but that would
     * depend on Logger to not contain mutable state.
     *
     * We could use Suppliers.memoizingSupplier here, but I micro-optimized to this implementation

   * FeatureSpecificTestSuiteBuilder.suppressing()}.
   */
  /*
   * TODO(cpovirk): or we could make HOLES_FORBIDDEN a feature. Or we could declare that
   * implementations are permitted to throw IAE if a hole is requested, and we could update
   * test*Hole to permit IAE. (But might this ignore genuine bugs?) But see the TODO above
   * testLower, which could make this all unnecessary
   */
  public static Method[] getHoleMethods() {

There have been discussions on embedding a Java runtime in the Gradle distribution.
This would allow users to run Gradle without having to install a Java runtime beforehand.
This capability could help increase Gradle adoption outside of the JVM ecosystem.

Gradle can be invoked in different ways:
* Through the [Gradle Wrapper](https://docs.gradle.org/8.8/userguide/gradle_wrapper.html)

        Node node = doResolve(link, classMetaData, listener);
        if (node != null) {
            return node;
        }

        listener.warning(String.format("Could not convert Javadoc link '%s'", link));
        Element element = document.createElement("UNHANDLED-LINK");
        element.appendChild(document.createTextNode(link));
        return element;
    }

    return backingMap;
  }

  @SuppressWarnings("unchecked") // value could not get in if not a T
  private <T extends B> @Nullable T trustedPut(
      TypeToken<@NonNull T> type, @ParametricNullness T value) {
    return (T) backingMap.put(type, value);
  }

  @SuppressWarnings("unchecked") // value could not get in if not a T
  private <T extends @NonNull B> @Nullable T trustedGet(TypeToken<T> type) {

      return unsafeDoBackward(b);
    }
  }

  /*
   * LegacyConverter violates the contract of Converter by allowing its doForward and doBackward
   * methods to accept null. We could avoid having unchecked casts in Converter.java itself if we
   * could perform a cast to LegacyConverter, but we can't because it's an internal-only class.
   *
   * TODO(cpovirk): So make it part of the open-source build, albeit package-private there?
   *