## What we expect from contributors

Please report this to https://github.com/markedjs/marked.`,e){let r="<p>An error occurred:</p><pre>"+O(n.message+"",!0)+"</pre>";return t?Promise.resolve(r):r}if(t)return Promise.reject(n);throw n}}};var M=new I;function g(l,e){return M.parse(l,e)}g.options=g.setOptions=function(l){return M.setOptions(l),g.defaults=M.defaults,Z(g.defaults),g};g.getDefaults=_;g.defaults=R;g.use=function(...l){return M.use(...

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...

        // 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

        assertProvideThrowsException("Test😀Classification");
    }

    // Helper method to assert that provide() throws ProvidedClassificationNotFoundException
    private void assertProvideThrowsException(String classificationName) {
        try {
            provider.provide(classificationName);
            fail("Should throw ProvidedClassificationNotFoundException for: " + classificationName);

The Wrapper then downloads the Gradle distribution (if necessary), starts the Launcher and runs the build, spawning and connecting to other processes such as the Daemon as required.

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.

        ],
        "parallelizationMethod": {
          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "build-cache-local",
          "build-profile",
          "ear",
          "instrumentation-agent-services",
          "logging",
          "messaging",
          "plugins-java-base",
          "problems",
          "problems-api",

This platform is agnostic to what exactly the purpose of the work is.
It might be creating an application, setting up development environments, orchestrating deployments, running simulations, etc.

This platform does not provide special support for a particular kind of automation. This is the responsibility of other platforms. 

It is made up of 3 architecture modules: