Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for isolation (0.15 sec)

  1. CONTRIBUTING.md

    * Keep commits discrete. Avoid including multiple unrelated changes in a single commit.
    * Keep commits self-contained. Avoid spreading a single change across multiple commits. A single commit should make sense in isolation.
    
    ### Testing changes
    
    After making changes, you can test your code in 2 ways:
    
    1. Run tests.
    - Run `./gradlew :<subproject>:quickTest` where `<subproject>` is the name of the subproject you've changed. 
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sat May 04 07:43:02 GMT 2024
    - 15.6K bytes
    - Viewed (0)
  2. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/NullabilityBreakingChangesRule.groovy

                }
            }
    
            if (!errors.isEmpty()) {
                def changes = errors + warnings
                return acceptOrReject(member, changes, Violation.error(member, changes.join(" ")))
            }
            if (!warnings.isEmpty()) {
                return Violation.warning(member, warnings.join(" "))
            }
            return null
        }
    
        private static List<Boolean> parametersNullabilityOf(CtBehavior behavior) {
    Groovy
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Sat Apr 13 10:04:28 GMT 2024
    - 5.4K bytes
    - Viewed (0)
  3. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy

            return repository.isOverride(method)
        }
    
        Violation acceptOrReject(JApiCompatibility member, Violation rejection) {
            List<String> changes = member.compatibilityChanges.collect { Violation.describe(it) }
            return acceptOrReject(member, changes, rejection)
        }
    
        Violation acceptOrReject(JApiCompatibility member, List<String> changes, Violation rejection) {
    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. .github/workflows/codeql-analysis.yml

          env:
            # Set the DEVELOCITY_ACCESS_KEY so that Gradle Build Scans are generated
            DEVELOCITY_ACCESS_KEY: ${{ secrets.GRADLE_ENTERPRISE_ACCESS_KEY }}
            # Potential stop-gap solution for ReadTimeout issues with the Gradle Build Cache
            # https://gradle.slack.com/archives/CHDLT99C6/p1636477584059200
            GRADLE_OPTS: -Dhttp.keepAlive=false
    
        - name: Compile with Gradle without Build Scan
    Others
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 09:13:16 GMT 2024
    - 4K bytes
    - Viewed (0)
  5. architecture/standards/0001-use-architectural-decision-records.md

    # ADR-0001 - Use Architectural Decision Records
    
    ## Date
    
    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:
    
    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)
  6. build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/upgrades/UpgradedProperties.java

         */
        public static boolean shouldAcceptForUpgradedProperty(JApiMethod jApiMethod, Violation violation, ViolationCheckContext context) {
            if (violation.getHumanExplanation().startsWith(SINCE_ERROR_MESSAGE)) {
                // We still want to report the violation if @since is not added to a method
                return false;
            }
    
    Java
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Apr 23 08:40:36 GMT 2024
    - 6.8K bytes
    - Viewed (0)
Back to top