- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 10 for isolation (0.34 sec)
-
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) -
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) -
Development.md
This is a collection of best practices for Gradle implementation. Should and should not do's. ## Error messages and suggestions Traditionally, if an error occurred, the error message and the possible solution were provided to the console via a single String in the corresponding exception. That meant possible solutions for Problems could be scattered all over the console output.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 06 22:54:40 GMT 2024 - 1.8K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/30_contributor_regression.yml
id: context attributes: label: Context (optional) description: | How has this issue affected you? What are you trying to accomplish? Providing context helps us come up with a solution that is most useful in the real world validations: required: false - type: textarea id: steps-to-reproduce attributes: label: Steps to Reproduce description: |
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 2.7K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/40_contributor_documentation.yml
id: context attributes: label: Context (optional) description: | How has this issue affected you? What are you trying to accomplish? Providing context helps us come up with a solution that is most useful in the real world validations: required: false - type: input id: page attributes: label: Page with the problem
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Jan 15 10:01:01 GMT 2024 - 1.6K bytes - Viewed (0) -
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) -
.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) -
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) -
.github/ISSUE_TEMPLATE/10_contributor_bug_report.yml
id: context attributes: label: Context (optional) description: | How has this issue affected you? What are you trying to accomplish? Providing context helps us come up with a solution that is most useful in the real world validations: required: false - type: textarea id: steps-to-reproduce attributes: label: Steps to Reproduce description: |
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 3K bytes - Viewed (0) -
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)