<p><la:message key="labels.menu_maintenance" /></p>
						</a></li></c:if>

				</ul></li></c:if>

			<c:if test="${fe:fileExists('/WEB-INF/view/common/admin/sidebar_extra.jsp')}">
				<c:import url="/WEB-INF/view/common/admin/sidebar_extra.jsp" />
			</c:if>
		</ul>
		</nav>
	</div>

 * <ul>
 *   <li>{@link org.apache.maven.api.cache.RequestCache} - The main interface for caching request results</li>
 *   <li>{@link org.apache.maven.api.cache.RequestCacheFactory} - Factory for creating cache instances</li>
 *   <li>{@link org.apache.maven.api.cache.CacheMetadata} - Configuration for cache behavior and lifecycle</li>
 * </ul>
 * <p>

 *
 * <p>The {@code Packaging} class is an immutable value object, ensuring that once a packaging type is defined, it cannot be changed.</p>
 *
 * <h2>Standard Packaging Types</h2>
 * <ul>
 *     <li>{@code jar}: Packages the project as a Java Archive (JAR) file.</li>
 *     <li>{@code war}: Packages the project as a Web Application Archive (WAR) file.</li>

 *
 * <p>The DataIndexHelper supports:</p>
 * <ul>
 *   <li>Concurrent crawling of multiple data configurations</li>
 *   <li>Thread pool management for crawler execution</li>
 *   <li>Session-based crawling with cleanup operations</li>
 *   <li>Old document deletion after successful crawling</li>
 *   <li>Crawling execution monitoring and timing</li>
 * </ul>
 */
public class DataIndexHelper {

			arg0="${f:h(pager.currentPageNumber)}"
			arg1="${f:h(pager.allPageCount)}"
			arg2="${f:h(pager.allRecordCount)}" />
	</div>
	<nav aria-label="...">
	</nav>
	<div class="col-sm-10">
		<ul class="pagination pagination-sm m-0 float-right">
			<c:if test="${pager.existPrePage}">
				<li class="page-item"><la:link
						styleClass="page-link"
						href="list/${pager.currentPageNumber - 1}">

 * system is initialized.
 *
 * <p>This package includes:</p>
 * <ul>
 *   <li>Basic logging interfaces and implementations</li>
 *   <li>Support for different logging levels (DEBUG, INFO, WARN, ERROR)</li>
 *   <li>Accumulating loggers for deferred output</li>
 * </ul>
 *
 * @since 4.0.0
 */

 *
 * <p>Valid:
 *
 * <ul>
 *   <li>Live: valid key/value are set
 *   <li>Loading: loading is pending
 * </ul>
 *
 * <p>Invalid:
 *
 * <ul>
 *   <li>Expired: time expired (key/value may still be set)
 *   <li>Collected: key/value was partially collected, but not yet cleaned up
 *   <li>Unset: marked as unset, awaiting cleanup or reuse
 * </ul>
 */
@GwtIncompatible

									</la:link></li>
							</c:if>
						</c:forEach>
					</ul>
				</c:if>
			</c:forEach>
			<c:forEach var="facetQueryView" items="${fe:facetQueryViewList()}">
				<ul class="list-group mb-2">
					<li class="list-group-item text-uppercase"><la:message
							key="${facetQueryView.title}" /></li>

 * second invocation, so implementors have made various choices, including:
 *
 * <ul>
 *   <li>returning the same iterator again
 *   <li>throwing an exception of some kind
 *   <li>or the usual, <i>robust</i> behavior, which all known {@link Collection} implementations
 *       have, of returning a new, independent iterator
 * </ul>
 *
 * <p>Because of this situation, any public method accepting an iterable should invoke the {@code

 *
 * <p>Key features include:</p>
 * <ul>
 *   <li>Build lifecycle execution control</li>
 *   <li>Project-specific configuration</li>
 *   <li>Goal execution and phase mapping</li>
 *   <li>Multi-module build coordination</li>
 * </ul>
 *
 * @see org.apache.maven.api.cli.Tools#MVN_CMD
 * @see org.apache.maven.api.cli.Tools#MVN_NAME
 * @since 4.0.0
 */