</properties>
	<profiles>
		<profile>
			<id>build</id>
			<activation>
				<activeByDefault>true</activeByDefault>
			</activation>
			<properties>
				<test.include.path>**/*Test.java</test.include.path>
				<test.command.args>--illegal-access=permit -Djava.awt.headless=true</test.command.args>
			</properties>
		</profile>
		<profile>
			<id>integrationTests</id>
			<properties>

core plugins in gradle/gradle, it's easy for an object to be created without applying its associated plugin. For instance, Spring has a plugin that uses the Checkstyle task directly without applying the Checkstyle plugin.

Until we can provide the same guarantees for core plugins, we need to be more conservative for existing classes and not follow best practices. This means conventions need to be set in both a plugin and the constructor. This keeps existing builds working, but it may complicate...

         * @return the parsed Query object
         */
        Query parse(final String query);
    }

    /**
     * Custom Lucene query parser that extends the standard QueryParser
     * to provide additional functionality for quoted queries.
     */
    protected static class LuceneQueryParser extends org.apache.lucene.queryparser.classic.QueryParser {

        /** The default field for queries */

        assertEquals("/error/error.jsp", FessHtmlPath.path_Error_ErrorJsp.getRoutingPath());
        assertEquals("/login/index.jsp", FessHtmlPath.path_Login_IndexJsp.getRoutingPath());
        assertEquals("/profile/index.jsp", FessHtmlPath.path_Profile_IndexJsp.getRoutingPath());
    }

    @Test
    public void test_uniquePaths() throws Exception {
        // Verify all paths are unique
        Set<String> paths = new HashSet<>();

          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<profiles version="12">
<profile kind="CodeFormatterProfile" name="DBFlute Style" version="12">
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_ellipsis" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_new_line_in_empty_annotation_declaration" value="insert"/>

 * A response list that extends List functionality and includes pagination and search metadata.
 * This class wraps search results with pagination information, facet responses, and query statistics.
 * It implements the List interface to provide standard list operations while adding search-specific
 * functionality such as page navigation, record counts, and query execution times.
 */
public class QueryResponseList implements List<Map<String, Object>> {

* 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.

            <option value="$PROJECT_DIR$/platforms/core-runtime/build-process-services" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/build-profile" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/build-state" />
            <option value="$PROJECT_DIR$/platforms/core-runtime/classloaders" />

     * for session management, so no specific logout URL is provided.
     *
     * @param user The user to logout
     * @return Always returns null as SPNEGO doesn't provide a logout URL
     */
    @Override
    public String logout(final FessUserBean user) {
        return null;
    }