- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 48 for leaving (0.05 seconds)
-
architecture/standards/0010-gradle-properties-naming.md
Previously, there was no formalization of property naming; only loose conventions were followed. While these conventions served relatively well in practice, they created gaps, resulting in a loss of uniformity in some cases and leaving friction in the process of naming new properties. ### Terminology **Public properties** are formally a part of the Public API. Public properties are **stable properties**: they CANNOT be renamed or removed without notice.
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Fri Mar 06 09:25:54 GMT 2026 - 8K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/llm/AbstractLlmClient.java
/** * Checks if the LLM response has empty/blank content with a "length" finish reason. * This typically indicates that a reasoning model consumed all tokens for internal * reasoning, leaving no tokens for actual output content. * * @param response the LLM chat response * @return true if content is empty/blank and finish reason is "length" */Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sat Mar 21 06:04:58 GMT 2026 - 72K bytes - Click Count (0) -
.gitignore
# ----- *.hprof # Work dirs # --------- /incoming-distributions /intTestHomeDir # Logs # ---- /*.log # Thread dumps for troubleshooting *.threaddump # ps output for cleaning up leaking Java processes *.psoutput # oh-my-zsh gradle plugin .gradletasknamecache # Added GE support maven support to the maven build in .teamcity, per the GE docs, this dir is NOT to be committed
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Wed Mar 11 16:15:24 GMT 2026 - 1.8K bytes - Click Count (0) -
src/main/webapp/js/marked.min.js
Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sun Mar 15 06:21:57 GMT 2026 - 41.5K bytes - Click Count (0) -
src/main/java/org/codelibs/fess/helper/ProtocolHelper.java
*/ public ProtocolHelper() { // Default constructor } /** * Initializes the protocol helper by loading configured protocols from FessConfig * and scanning for available protocol handlers in the classpath. * This method is called automatically after bean construction. */ @PostConstructCreated: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Thu Mar 26 13:59:25 GMT 2026 - 12.4K bytes - Click Count (1) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/ReleaseNotesTransformer.java
Element heading = document.body().select("h2").first(); List<Element> inSection = new ArrayList<>(); inSection.add(heading); Element next = heading.nextElementSibling(); while (true) { if (next == null || next.tagName().equals("h2")) { Element section = heading.before("<section class='topic'/>").previousElementSibling();
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Tue Mar 03 01:59:51 GMT 2026 - 11.3K bytes - Click Count (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/FindBrokenInternalLinks.java
Created: Wed Apr 01 11:36:16 GMT 2026 - Last Modified: Thu Mar 12 23:22:57 GMT 2026 - 12.8K bytes - Click Count (0) -
architecture/standards/0007-java-pre-requisite.md
- PROPOSED on 2024-12-20 ## Context ### Embedding a Java runtime in the Gradle distribution There have been discussions on embedding a Java runtime in the Gradle distribution. This would allow users to run Gradle without having to install a Java runtime beforehand. This capability could help increase Gradle adoption outside of the JVM ecosystem. Gradle can be invoked in different ways:
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) -
src/test/java/org/codelibs/fess/job/SuggestJobTest.java
@Override public String getRealPath(String path) { if (path == null) { return tempDir.getAbsolutePath(); } // Remove leading slash if present if (path.startsWith("/")) { path = path.substring(1); } return new File(tempDir, path.replace("/", File.separator)).getAbsolutePath(); }Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Fri Mar 13 23:01:26 GMT 2026 - 31.6K bytes - Click Count (0) -
architecture/standards/0002-avoid-using-java-serialization.md
Java serialization is inherently Java-centric and does not support cross-language scenarios well. - **Type Safety:** Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors. ## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized.
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)