* include compilers, interpreters, and other tools that are necessary
 * for building a project in a specific environment.</p>
 *
 * <p>Toolchains are defined in the Maven toolchains.xml file and can be
 * referenced in the project's POM file. This allows for greater flexibility
 * and control over the build environment, enabling developers to specify
 * the exact versions of tools they wish to use.</p>
 *
 * <p>

@setlocal

@REM ==== START VALIDATION ====
if not "%JAVA_HOME%" == "" goto OkJHome

echo. >&2
echo Error: JAVA_HOME not found in your environment. >&2
echo Please set the JAVA_HOME variable in your environment to match the >&2
echo location of your Java installation. >&2
echo. >&2
goto error

:OkJHome
if exist "%JAVA_HOME%\bin\java.exe" goto init

echo. >&2

The hermetic Python version is controlled by `HERMETIC_PYTHON_VERSION`
environment variable, which could be setin one of the following ways:

```
# Either add an entry to your `.bazelrc` file
build --repo_env=HERMETIC_PYTHON_VERSION=3.12

# OR pass it directly to your specific build command
bazel build <target> --repo_env=HERMETIC_PYTHON_VERSION=3.12

# OR set the environment variable globally in your shell:
export HERMETIC_PYTHON_VERSION=3.12

# Properties used to build to the DEB package
#

# Environment file
packaging.env.file=/etc/default/fess

# Simple marker to check that properties are correctly overridden
packaging.type=deb

# Custom header for package scripts
packaging.scripts.header=#!/bin/sh${line.separator}set -e

Homepage: https://github.com/codelibs/fess
Description: Enterprise Search Server: Fess

@REM specific language governing permissions and limitations
@REM under the License.

@REM -----------------------------------------------------------------------------
@REM Apache Maven Upgrade Script
@REM
@REM Environment Variable Prerequisites
@REM
@REM   JAVA_HOME           (Optional) Points to a Java installation.
@REM   MAVEN_OPTS          (Optional) Java runtime options used when Maven is executed.

# This file contains the initial defaults for go command configuration.
# Values set by 'go env -w' and written to the user's go/env file override these.
# The environment overrides everything else.

# Use the Go module mirror and checksum database by default.
# See https://proxy.golang.org for details.
GOPROXY=https://proxy.golang.org,direct
GOSUMDB=sum.golang.org

# Automatically download newer toolchains as directed by go.mod files.

-   Continuous jobs (Run on every GitHub commit)
    -   Uses `pycpp.sh`
-   Presubmit jobs (Run on every GitHub PR)
    -   Uses `pycpp.sh`, `code_check_changed_files.sh`

These "env" files match up with an environment matrix that roughly covers:

-   Different Python versions
-   Linux, MacOS, and Windows machines (these pool definitions are internal)
-   x86 and arm64
-   CPU-only, or with NVIDIA CUDA support (Linux only), or with TPUs

        } catch (Exception e) {
            // Expected in test environment
            assertTrue(true);
        }
    }

    public void test_getUserInfo_nullUserCode() {
        try {
            var result = searchLogHelper.getUserInfo(null);
            assertFalse(result.isPresent());
        } catch (Exception e) {
            // Expected in test environment
            assertTrue(true);
        }
    }

<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<include path="convention.xml" />
	<include path="lastaflute.xml" />
	
	<!-- Register systemProperties for test environment -->
	<component name="systemProperties" class="org.codelibs.fess.unit.TestSystemProperties" />