The main logic with ADRs is to describe (architectural) decisions made:

* To provide best practices and solutions we (as the *build tool* team) want to promote.
* To avoid asking the same thing multiple times during code review.
* To explain *rejected solutions*, for now, and future development, in case they are proposed again.

Practically every Gradle feature is behind a flag, and additional sub-flags or options provide further control.

The number of existing Gradle properties is already in the double digits. More properties will be added in the future.
Although properties offer the benefit of precise user-side control and support gradual evolution practices, the high number of properties also presents challenges.

&&(R(Ne,["tbody"]),delete Oe.tbody),e.TRUSTED_TYPES_POLICY){if("function"!=typeof e.TRUSTED_TYPES_POLICY.createHTML)throw S('TRUSTED_TYPES_POLICY configuration option must provide a "createHTML" hook.');if("function"!=typeof e.TRUSTED_TYPES_POLICY.createScriptURL)throw S('TRUSTED_TYPES_POLICY configuration option must provide a "createScriptURL" hook.');le=e.TRUSTED_TYPES_POLICY,ce=le.createHTML("")}else void 0===le&&(le=function(e,t){if("object"!=typeof e||"function"!=typeof e.createPolicy)return...

							<i class="fa fa-arrow-circle-left" aria-hidden="true"></i>
							<la:message key="labels.profile.back" />
						</la:link>
						<button type="submit" name="changePassword"
							class="btn btn-success"
							value="<la:message key="labels.profile.update"/>">
							<i class="fa fa-pencil-alt" aria-hidden="true"></i>
							<la:message key="labels.profile.update" />
						</button>
					</div>
				</la:form>
			</div>
		</div>

        upload.assertTasks("prepReleaseNightly uploadAll")
        assertEquals(expectedGradleParams, upload.gradleParams)

        val promote = gradleStep(steps, 2)
        promote.assertTasks("prepReleaseNightly promoteReleaseNightly")
        assertEquals(expectedGradleParams, promote.gradleParams)
    }

    @Test
    fun `start release cycle promotion build type runs one gradle invocation`() {

							<i class="fa fa-arrow-circle-left" aria-hidden="true"></i>
							<la:message key="labels.profile.back" />
						</la:link>
						<button type="submit" name="changePassword"
							class="btn btn-success"
							value="<la:message key="labels.profile.update"/>">
							<i class="fa fa-pencil-alt" aria-hidden="true"></i>
							<la:message key="labels.profile.update" />
						</button>
					</div>
				</la:form>
			</div>
		</div>

        // Then
        TimeZone first = provider.provide();
        TimeZone second = provider.provide();
        assertSame(first, second, "Provider should return the same TimeZone instance");
    }

    @Test
    public void test_createFinalTimeZoneProvider_toStringContainsTimeZoneId() {
        // When

    // Search Execute
    // ==============

    /**
     * Displays the profile index page.
     *
     * @return the HTML response
     */
    @Execute
    public HtmlResponse index() {
        return asIndexHtml();
    }

    /**
     * Changes the user password.
     *
     * @param form the profile form
     * @return the HTML response
     */
    @Execute

        // Test profile related labels
        assertEquals("{labels.profile}", FessLabels.LABELS_PROFILE);
        assertEquals("{labels.profile.title}", FessLabels.LABELS_PROFILE_TITLE);
        assertEquals("{labels.profile.update}", FessLabels.LABELS_PROFILE_UPDATE);
        assertEquals("{labels.profile.back}", FessLabels.LABELS_PROFILE_BACK);

- [ ] Provide integration tests (under `<subproject>/src/integTest`) to verify changes from a user perspective.
- [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic.
- [ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.