Scribd Logo
Upload

Welcome to Scribd!

  • Formatting

    Uploaded by

    vivek
    5 views1 page
    The document discusses code formatting for Solr projects. It states that starting with a specific issue, Java code must comply with Google formatting conventions. Running a 'tidy' Gradle task will reformat code to match the conventions prior to running checks. There is no way to exclude sections from formatting, though files can be excluded by modifying the build script.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document discusses code formatting for Solr projects. It states that starting with a specific issue, Java code must comply with Google formatting conventions. Running a 'tidy' Gradle task will reformat code to match the conventions prior to running checks. There is no way to exclude sections from formatting, though files can be excluded by modifying the build script.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    5 views1 page

    Formatting

    Uploaded by

    vivek
    The document discusses code formatting for Solr projects. It states that starting with a specific issue, Java code must comply with Google formatting conventions. Running a 'tidy' Gradle task will reformat code to match the conventions prior to running checks. There is no way to exclude sections from formatting, though files can be excluded by modifying the build script.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Code formatting

    ===============

    ---
    Starting with (SOLR-14920) Java code is enforced to comply with
    google-java-format conventions. In theory you shouldn't worry about
    what the convention actually looks like - write the code in any way
    you like and then run:

    ./gradlew tidy

    prior to running your regular precommit checks. This will reformat


    your code so that it complies with the convention and passes gradle
    'check' task.

    IMPORTANT: There is *no* way to mark sections of the code as excluded


    from formatting. This is by design and cannot be altered. In vast
    majority of cases the formatter will do a great job of cleaning up the
    code. To exclude files from being formatted investigate the spotless.gradle
    build script.
    ---

    You might also like