- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 29 for houver (0.05 seconds)
-
src/main/resources/fess_indices/_aws/fess.json
"esteja", "estejamos", "estejam", "estivesse", "estivéssemos", "estivessem", "estiver", "estivermos", "estiverem", "hei", "há", "havemos", "hão", "houve", "houvemos", "houveram", "houvera", "houvéramos", "haja", "hajamos", "hajam", "houvesse", "houvéssemos", "houvessem", "houver", "houvermos", "houverem", "houverei", "houverá", "houveremos", "houverão", "houveria", "houveríamos", "houveriam", "sou", "somos", "são", "era", "éramos", "eram", "fui", "foi", "fomos", "foram", "fora", "fôramos", "seja", "sejamos",...
Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sun Mar 15 07:52:55 GMT 2026 - 117.5K bytes - Click Count (0) -
src/main/resources/fess_indices/_cloud/fess.json
"esteja", "estejamos", "estejam", "estivesse", "estivéssemos", "estivessem", "estiver", "estivermos", "estiverem", "hei", "há", "havemos", "hão", "houve", "houvemos", "houveram", "houvera", "houvéramos", "haja", "hajamos", "hajam", "houvesse", "houvéssemos", "houvessem", "houver", "houvermos", "houverem", "houverei", "houverá", "houveremos", "houverão", "houveria", "houveríamos", "houveriam", "sou", "somos", "são", "era", "éramos", "eram", "fui", "foi", "fomos", "foram", "fora", "fôramos", "seja", "sejamos",...
Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sun Mar 15 07:52:55 GMT 2026 - 117.5K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/ldap/LdapManager.java
* @param envSupplier The environment supplier. * @return The directory context holder. */ protected DirContextHolder getDirContext(final Supplier<Hashtable<String, String>> envSupplier) { DirContextHolder holder = contextLocal.get(); if (holder != null) { holder.inc(); return holder; } final Hashtable<String, String> env = envSupplier.get();Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Fri Jan 02 08:06:20 GMT 2026 - 85.2K bytes - Click Count (0) -
architecture/standards/0007-java-pre-requisite.md
Embedding a Java runtime in the distribution would provide some benefits, such as allowing the Launcher, Daemon and Workers to run on it, removing the prerequisite of an installed Java runtime. However, this does not fully remove the prerequisite, as the Wrapper itself would still need an installed Java runtime to execute. Gradle needs a solution that covers the use-case of starting the Wrapper itself as well given its importance.
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Thu Mar 05 12:39:41 GMT 2026 - 3.2K bytes - Click Count (0) -
CONTRIBUTING.md
You can share your interest in fixing the issue by commenting on it. If somebody shared their interest in the issue, please consider letting them work on it. However, if there are no changes for more than a week, it's safe to assume that the issue is up for grabs. There is no need to ask for an assignment or for permission to work on those issues, just comment and start working on it.
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Fri Mar 27 18:43:39 GMT 2026 - 19.1K bytes - Click Count (0) -
.teamcity/src/main/kotlin/model/CIBuildModel.kt
QUICK(true, true, true, 120, 4), // Include cross version tests, these take care of selecting a very small set of versions to cover when run as part of this stage, including the current version PLATFORM(true, true, true), // Cross version tests select a small set of versions to cover when run as part of this stage
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Tue Jan 20 03:53:25 GMT 2026 - 27.5K bytes - Click Count (0) -
architecture/standards/0005-introduce-core-ui-architecture-module.md
The UI architecture module uses the core runtime architecture module. It provides APIs that are used by the other modules and platforms. This ADR does not specify the owner of this new architecture module. However, as a separate module, it can be assigned ownership independently of the other core services. ## Consequences - Introduce the module and move the services and their implementations.
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Thu Mar 05 12:39:41 GMT 2026 - 1.3K bytes - Click Count (0) -
src/main/resources/fess_label_en.properties
labels.searchlog_log_type_search_zeroclick=Zero Click Count labels.searchlog_log_type_search_count_hour=Search Count/Hour labels.searchlog_log_type_search_count_day=Search Count/Day labels.searchlog_log_type_search_user_hour=User Count/Hour labels.searchlog_log_type_search_user_day=User Count/Day labels.searchlog_log_type_search_reqtimeavg_hour=Request Average Time/Hour labels.searchlog_log_type_search_reqtimeavg_day=Request Average Time/Day
Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sat Mar 28 11:54:13 GMT 2026 - 48.9K bytes - Click Count (0) -
architecture/standards/0002-avoid-using-java-serialization.md
## Status - ACCEPTED on 2023-12-01 ## Context In Gradle we often need to serialize in-memory objects for caching, or to transmit them across process barriers, etc. Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks: - **Performance:** Java's built-in serialization mechanism is often slower compared to other serialization solutions.
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Thu Mar 05 14:05:45 GMT 2026 - 2.3K bytes - Click Count (0) -
src/test/java/org/codelibs/fess/helper/IntervalControlHelperTest.java
try { IntervalControlHelper.parseTime("24:00"); fail("Should throw FessSystemException"); } catch (FessSystemException e) { assertEquals("Invalid hour value: 24 in time: 24:00. Hour must be between 0 and 23", e.getMessage()); } try { IntervalControlHelper.parseTime("12:60"); fail("Should throw FessSystemException");Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Wed Jan 14 14:29:07 GMT 2026 - 13.6K bytes - Click Count (0)