*/
object ArchitectureDataType {
    /**
     * JSON containing platforms data. See root settings file for more information.
     */
    val PLATFORMS = "platforms"

    /**
     * JSON containing package-info data. See root settings file for more information.
     */
    val PACKAGE_INFO = "package-info"

See [Architecture decisions records](standards) for the list of ADRs.
Be aware these are very technical descriptions of the decisions, and you might find the documentation below more useful as an introduction to the internals of Gradle.

## Architecture overview

### Platform architecture

Gradle is arranged into several coarse-grained components called "platforms".

        }
        // It would be nice if we could be more selective about which variants to apply this to.
        // TODO https://github.com/gradle/gradle/issues/11831#issuecomment-580686994
        artifactTypes.getByName("jar") {
            attributes.attribute(minified, java.lang.Boolean.FALSE)
        }
        /*
         * It would perhaps be better to do this more selectively instead of applying this transform so broadly and having

labels.crawling_info_CrawlerStartTime=Hora de início do rastreador
labels.crawling_info_CrawlerEndTime=Hora de término do rastreador
labels.crawling_info_CrawlerExecTime=Tempo de execução do rastreador
labels.crawling_info_CrawlerStatus=Estado do rastreador
labels.crawling_info_WebFsCrawlExecTime=Tempo de execução do rastreamento (Web/Arquivo)
labels.crawling_info_WebFsCrawlStartTime=Hora de início do rastreamento (Web/Arquivo)

* **Better searchability**: Finding code and documentation becomes more predictable
* **Reduced review friction**: Less time spent on spelling corrections during PR reviews
* **Professional appearance**: Consistent APIs and documentation appear more polished
* **Clearer contribution guidelines**: [CONTRIBUTING.md](../../CONTRIBUTING.md) now includes this requirement

# Build execution model

At the highest level, Gradle's execution model is quite simple:

Below is the protocol in some more detail:

1. The client looks for a compatible idle daemon. If there isn't one, it starts a new daemon.
2. The client connects to the idle daemon and sends it a request to do some work. If the daemon is no longer running, the client starts again.

If you are looking for a contribution that is more substantial, you can look at the [help wanted issues](https://github.com/gradle/gradle/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%F0%9F%8C%B3%20help%20wanted%22).
These issues are more complex and might be challenging for first-time contributors.

You can share your interest in fixing the issue by commenting on it.

labels.crawling_info_thread_dump=Dump thread
labels.crawling_info_CrawlerStartTime=Ora di inizio crawler
labels.crawling_info_CrawlerEndTime=Ora di fine crawler
labels.crawling_info_CrawlerExecTime=Tempo di esecuzione crawler
labels.crawling_info_CrawlerStatus=Stato crawler
labels.crawling_info_WebFsCrawlExecTime=Tempo di esecuzione scansione (Web/File)
labels.crawling_info_WebFsCrawlStartTime=Ora di inizio scansione (Web/File)

A typical platform builds on other platforms in order to add more capabilities, for example, to add support for a particular language.

See the [discovery document](https://docs.google.com/document/d/1-oKG23gLdx2D2uJvzir31AhDFyqSf81LDESfKKCU28c/edit#heading=h.pps74pn68uvk) (internal document) for more context.

### Platforms

The platforms and their architecture modules are:

* IDE warnings become more accurate, reducing warnings fatigue.
* Public API nullability annotations become closer to reality.
* Java compilation of Gradle code suffers from small performance penalty (up to 10%).
* Time has to be allocated to clean up existing projects.
* One has to write NullAway-conformant code even when hacking.
* Some patterns used to satisfy NullAway can be slightly more verbose.