<groupId>com.esotericsoftware</groupId>
			<artifactId>kryo</artifactId>
			<version>${kryo.version}</version>
		</dependency>

		<!-- suggest library -->
		<dependency>
			<groupId>org.codelibs.fess</groupId>
			<artifactId>fess-suggest</artifactId>
			<version>${suggest.version}</version>
		</dependency>

		<!-- fileupload -->
		<dependency>
			<groupId>org.apache.commons</groupId>

import org.codelibs.fess.app.web.admin.searchlog.AdminSearchlogAction;
import org.codelibs.fess.app.web.admin.sereq.AdminSereqAction;
import org.codelibs.fess.app.web.admin.storage.AdminStorageAction;
import org.codelibs.fess.app.web.admin.suggest.AdminSuggestAction;
import org.codelibs.fess.app.web.admin.systeminfo.AdminSysteminfoAction;
import org.codelibs.fess.app.web.admin.user.AdminUserAction;
import org.codelibs.fess.app.web.admin.webauth.AdminWebauthAction;

If they need to be renamed or removed (together or separately from the feature itself), they MUST go through a deprecation cycle and the actual property change MUST happen in a major release.
Since the naming of the properties no longer suggests they are experimental, we want to ensure users are aware if the current property stops having an effect.
Since the underlying feature is incubating, its actual behavior can still change or be removed in the minor releases.

        setConfig(100, 50);
        testableFilter.setCpuPercent((short) 60);

        String[] apiPaths = { "/api/v1/search", "/api/v1/documents", "/api/v2/suggest" };
        for (String path : apiPaths) {
            resetMocks();
            mockRequest.setRequestURI(path);
            testableFilter.doFilter(mockRequest, mockResponse, mockFilterChain);

                                        </la:select>
                                    </div>
                                </div>
                                    <%-- Suggest --%>
                                <h4><la:message key="labels.general_menu_suggest"/></h4>
                                <div class="form-group row">