<li class="page-item"><la:link
                                                        styleClass="page-link"
                                                        href="list/${labelTypePager.currentPageNumber - 1}">
                                                    <la:message key="labels.prev_page"/>
                                                </la:link></li>

 *
 * <ul>
 *   <li>An annotation named just "Suppress" might someday be treated by a non-Android tool as a
 *       suppression. This would follow the precedent of many of our annotation processors, which
 *       look for any annotation named, e.g., "GwtIncompatible," regardless of package.
 *   <li>An annotation named just "Suppress" might suggest to users that the test is suppressed

                        <ol class="breadcrumb float-sm-right">
                            <li class="breadcrumb-item"><la:link href="/admin/dict">
                                <la:message key="labels.dict_list_link"/>
                            </la:link></li>
                            <li class="breadcrumb-item"><la:message key="labels.dict_stemmeroverride_list_link"/></li>
                        </ol>
                    </div>
                </div>

                            </la:link></li>
                            <c:if test="${crudMode == 1}">
                                <li class="breadcrumb-item active"><la:message
                                        key="labels.dict_mapping_link_create"/></li>
                            </c:if>
                            <c:if test="${crudMode == 2}">
                                <li class="breadcrumb-item active"><la:message

                            <li class="breadcrumb-item"><la:link href="/admin/crawlinginfo">
                                <la:message key="labels.joblog_link_list"/>
                            </la:link></li>
                            <li class="breadcrumb-item active"><la:message
                                    key="labels.joblog_link_details"/></li>
                        </ol>
                    </div>

                            <li class="breadcrumb-item"><la:link href="/admin/wizard/">
                                <la:message key="labels.wizard_start_title"/>
                            </la:link></li>
                            <li class="breadcrumb-item"><la:message key="labels.wizard_crawling_config_title"/></li>
                            <li class="breadcrumb-item active"><la:message

 * Benchmarks (as of December 2011) show that:
 *
 * <ul>
 *   <li>for an unnested {@code lock()} and {@code unlock()}, a cycle detecting lock takes 38ns as
 *       opposed to the 24ns taken by a plain lock.
 *   <li>for nested locking, the cost increases with the depth of the nesting:
 *       <ul>
 *         <li>2 levels: average of 64ns per lock()/unlock()
 *         <li>3 levels: average of 77ns per lock()/unlock()

 * terms</a>):
 *
 * <ul>
 *   <li>directed graphs
 *   <li>undirected graphs
 *   <li>graphs that do/don't allow parallel edges
 *   <li>graphs that do/don't allow self-loops
 *   <li>graphs whose nodes/edges are insertion-ordered, sorted, or unordered
 *   <li>graphs whose edges are <a

     *
     * <ul>
     *   <li>If {@link #MODULES} path type is also set, then the dependency can be placed either on the
     *       class path or on the module path, but only one of those. The choice is up to the plugin,
     *       possibly using heuristic rules (Maven 3 behavior).</li>
     *   <li>If a {@link #patchModule(String)} is also set and the main JAR file is placed on the module path,

 * which provides functionality for upgrading Maven projects and dependencies.</p>
 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Project upgrade capabilities</li>
 *   <li>Dependency version management</li>
 *   <li>Configuration migration</li>
 *   <li>Interactive upgrade workflows</li>
 * </ul>
 *
 * @see org.apache.maven.api.cli.Tools#MVNUP_CMD
 * @see org.apache.maven.api.cli.Tools#MVNUP_NAME
 * @since 4.0.0
 */