from(files(basePath.file("build.versions.toml")))
        }
        val sharedVersions = basePath.file("shared-versions.properties").asFile.inputStream().use {
            Properties().apply { load(it) }
        }
        all {
            sharedVersions.forEach { key, value ->
                version(key.toString(), value.toString())
            }
        }
    }

        updateProperties(fetchedVersions)
    }

    private
    fun getPluginIds(): List<String> {
        val props = Properties()
        propertiesFile.get().asFile.reader().use { input ->
            props.load(input)
        }
        return props.keys.map { it as String }.sorted()
    }

    private
    fun fetchLatestVersions(pluginIds: List<String>): List<TestedVersion> =
        pluginIds

    private static final Logger logger = LogManager.getLogger(LoadControlMonitorTarget.class);

    private final SystemHelper systemHelper;

    private int consecutiveFailures = 0;

    /**
     * Constructs a new load control monitor target.
     *
     * @param systemHelper the system helper to update with CPU usage
     */
    public LoadControlMonitorTarget(final SystemHelper systemHelper) {
        this.systemHelper = systemHelper;

            setFeature("http://xml.org/sax/features/external-parameter-entities", false)
            setFeature("http://apache.org/xml/features/nonvalidating/load-external-dtd", false)
            isExpandEntityReferences = false
            setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true)
            setAttribute(XMLConstants.ACCESS_EXTERNAL_DTD, "")

Fess를 사용해보는 방법은 두 가지가 있습니다. 첫 번째는 직접 다운로드하여 설치하는 방법이며, 두 번째는 [Docker](https://www.docker.com/products/docker-engine)를 사용하는 방법입니다.

### 다운로드 및 설치/실행

Fess 15.3이 현재 사용 가능하며, [릴리스 페이지](https://github.com/codelibs/fess/releases "download")에서 다운로드할 수 있습니다. 다운로드는 deb, rpm, zip의 세 가지 형식으로 제공됩니다.

다음 명령은 zip 다운로드 사용 방법을 보여줍니다:

    $ unzip fess-15.3.x.zip
    $ cd fess-15.3.x
    $ ./bin/fess

    //                                                                        ============

    /**
     * Saves informational messages to the session.
     * The messages will be displayed to the user on the next page load.
     *
     * @param validationMessagesLambda a lambda function to configure the messages
     */
    protected void saveInfo(final VaMessenger<FessMessages> validationMessagesLambda) {

					<li class="nav-item">
						<a href="${fe:url('/admin/backup/')}" class="nav-link <c:if test="${param.menuType=='backup'}">active</c:if>" <c:if test="${param.menuType=='backup'}">aria-current="page"</c:if>>
							<i class='fa fa-download nav-icon' aria-hidden="true"></i>
							<p><la:message key="labels.menu_backup" /></p>
						</a></li></c:if>

					<c:if test="${fe:permission('admin-maintenance-view')}">
					<li class="nav-item">

        assertEquals("replacement", result);
    }

    @Test
    public void test_load_withoutPathMappingBhv() {
        final PathMappingHelper helper = new PathMappingHelper();
        int result = helper.load();
        assertEquals(0, result);
    }

    @Test
    public void test_init_called() {
        final PathMappingHelper helper = new PathMappingHelper();
        helper.init();

However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading
* Redundant null checks may increase binary size, hurt performance, and increase cognitive load for readers
* Missing null checks may cause NullPointerException
* Bridging with Kotlin code is polluted with platform types
* Some public APIs have incorrect nullability annotations (both overly restrictive and overly permissive)

            timeZone = TimeZone.getTimeZone("UTC")
        }

        fun readBuildReceiptFromString(buildReceipt: String) =
            Properties().apply { load(buildReceipt.reader()) }

        const val buildReceiptFileName = "build-receipt.properties"
        const val buildReceiptLocation = "org/gradle/$buildReceiptFileName"
    }

    @get:Input