Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for Document (0.15 sec)

  1. build-logic/documentation/src/main/groovy/gradlebuild/docs/ReleaseNotesTransformer.java

            addCssToHead(document);
            addJavascriptToHead(document);
    
            wrapH2InSectionTopic(document);
            addAnchorsForHeadings(document);
            document.body().prepend("<h1>Gradle Release Notes</h1>");
            addTOC(document);
            wrapContentInContainer(document);
    
            String rewritten = document.body().html();
            // Turn Gradle Jira issue numbers into issue links
    Java
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Thu Apr 25 04:49:56 GMT 2024
    - 7.7K bytes
    - Viewed (0)
  2. architecture/standards/0004-use-a-platform-architecture.md

    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:
    
    #### Core automation platform
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sun Feb 25 22:19:29 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  3. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy

                          In that case, you can publish a new snapshot from the release branch. This will update `released-versions.json` on `master`.
                          See <a href="https://docs.google.com/document/d/1KA5yI4HL18qOeXjXLTMMD_upkDbNUzTDGNfBGYdQlYw/edit#heading=h.9yqcmqviz47z">the documentation</a> for more details.
                      </div>
                    </div>
                    </p>
                    <p>
    Groovy
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Apr 23 08:40:36 GMT 2024
    - 10.4K bytes
    - Viewed (0)
  4. .cm/javadoc_on_new_files.cm

              color: {{ colors.yellow }}
          - action: add-comment@v1
            args:
              comment: |
                :warning: This PR creates new top-level Java classes, but has no Javadoc present. Please document all top-level classes with Javadoc.
    
    is:
      java: {{ files | extensions | match(term='java') | every }}
      new: {{ source.diff.files | map(attr='original_file') | match(regex=r/^$/) | some }}
    
    colors:
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  5. architecture/standards/0001-use-architectural-decision-records.md

    2023-12-01
    
    ## Context
    
    In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development.
    
    We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:
    
    * They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sat Mar 02 21:54:40 GMT 2024
    - 2.8K bytes
    - Viewed (0)
Back to top