# ADR-0010 - Gradle properties naming

## Status

- ACCEPTED on 2026-03-05
- PROPOSED on 2026-02-26

## Context

[Gradle properties](https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_configuration_properties)
are flags that allow build engineers to opt into and out of features of Gradle Runtime or Core Plugins.
Practically every Gradle feature is behind a flag, and additional sub-flags or options provide further control.

# logging

# Application packages for logging.
logging.app.packages=org.codelibs,org.dbflute,org.lastaflute
# Whether to enable search docs logging.
logging.search.docs.enabled=true
# Fields to log for search docs.
logging.search.docs.fields=filetype,created,click_count,title,doc_id,url,score,site,filename,host,digest,boost,mimetype,favorite_count,_id,lang,last_modified,content_length,timestamp

extends BaseComponent {\n  constructor(element, config) {\n    super(element, config)\n\n    this._popper = null\n    this._parent = this._element.parentNode // dropdown wrapper\n    // TODO: v6 revert #37011 & change markup https://getbootstrap.com/docs/5.3/forms/input-group/\n    this._menu = SelectorEngine.next(this._element, SELECTOR_MENU)[0] ||\n      SelectorEngine.prev(this._element, SELECTOR_MENU)[0] ||\n      SelectorEngine.findOne(SELECTOR_MENU, this._parent)\n    this._inNavbar = this._detectNavbar()\n...

    /**
     * Get the value for the key 'logging.search.docs.enabled'. <br>
     * The value is, e.g. true <br>
     * comment: Whether to enable search docs logging.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getLoggingSearchDocsEnabled();

    /**
     * Is the property for the key 'logging.search.docs.enabled' true? <br>
     * The value is, e.g. true <br>

element receiving programmatic focus was a keyboard interaction,\n// or the browser has somehow determined that the user is primarily a keyboard user and/or\n// wants focus outlines to always be presented.\n//\n// See https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible\n// and https://developer.paciellogroup.com/blog/2018/03/focus-visible-and-backwards-compatibility/\n[tabindex=\"-1\"]:focus:not(:focus-visible) {\n  outline: 0 !important;\n}\n\n\n// Content grouping\n//\n// 1. Add the correct...

element receiving programmatic focus was a keyboard interaction,\n// or the browser has somehow determined that the user is primarily a keyboard user and/or\n// wants focus outlines to always be presented.\n//\n// See https://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible\n// and https://developer.paciellogroup.com/blog/2018/03/focus-visible-and-backwards-compatibility/\n[tabindex=\"-1\"]:focus:not(:focus-visible) {\n  outline: 0 !important;\n}\n\n\n// Content grouping\n//\n// 1. Add the correct...