}
                    }
                } catch (final Exception e) {
                    logger.log(Level.WARNING, e, () -> {
                        final String canonicalPath = possibleJar.getCanonicalPath();
                        return "Failed to read JAR file: path=" + canonicalPath;
                    });
                }

    private static final Logger LOGGER = LoggerFactory.getLogger(DefaultGenerationListener.class);
    private final LinkedList<String> contextStack = new LinkedList<String>();

    @Override
    public void warning(String message) {
        LOGGER.warn(String.format("%s: %s", contextStack.getFirst(), message));
    }

    @Override
    public void start(String context) {
        contextStack.addFirst(context);
    }

            // TODO: Maybe this could be simplified by not using the copy infrastructure and just
            // calling the FilterReader ourselves.  We're just taking one file and turning it into another.

            // The order here is important! tokens are inserted by the transformer
            Map<String, Object> parameters = new HashMap<>();

import org.codelibs.fess.util.ComponentUtil;
import org.opensearch.search.rescore.QueryRescorerBuilder;
import org.opensearch.search.rescore.RescorerBuilder;

/**
 * Learning to Rank query rescorer implementation.
 */
public class LtrQueryRescorer implements QueryRescorer {

    /**
     * Default constructor.
     */
    public LtrQueryRescorer() {
        // Default constructor

                        group = "verification"
                        description = "Ensures the accepted api changes file is kept alphabetically ordered to make merging changes to it easier"
                        apiChangesDirectory = layout.projectDirectory.dir("${ TextUtil.normaliseFileSeparators(firstAcceptedApiChangesFile.parentFile.absolutePath) }")
                    }

							title="<la:message key="labels.development_mode_warning" />"
						><a class="nav-link active" href="${installationLink}" target="_olh"><i
								class="fa fa-exclamation-triangle text-warning" aria-hidden="true"
							></i></a></li>
					</c:if>
					<c:choose>
						<c:when test="${!empty username && username != 'guest'}">
							<li class="nav-item">
								<div class="dropdown">

							title="<la:message key="labels.development_mode_warning" />"
						><a class="nav-link active" href="${installationLink}" target="_olh"><i
								class="fa fa-exclamation-triangle text-warning" aria-hidden="true"
							></i></a></li>
					</c:if>
					<c:choose>
						<c:when test="${!empty username && username != 'guest'}">
							<li class="nav-item">
								<div class="dropdown">

                                        </div>
                                    </c:if>
                                    <c:if test="${running}">
                                        <button type="submit" class="btn btn-warning" name="threaddump"
                                                value="<la:message key="labels.crawling_info_thread_dump" />">
                                            <i class="fa fa-bolt" aria-hidden="true"></i>

and there are no missing null checks.

## Decision

Use "NullAway" in JSpecify mode to check for null-related errors in Java code.

Consider improper uses of `null` detected by NullAway a compilation error (not a warning, and not a separate CI job to test).

Do not suppress NullAway errors without a justification.
Prefer rearranging the code to avoid the error, unless there is a provable performance penalty or a significant loss of code readability.

 * remain in their original namespace. This reduces the final Gradle distribution
 * size and makes us more conscious of which parts of a library we really need.
 *
 * WARNING: if you decide to do the minification by hand, make sure that you cover all paths of loading classes:
 * reflection, dynamic loading, etc. and understand how the library works internally.