- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for alphabetical (0.16 sec)
-
build-logic/binary-compatibility/src/main/kotlin/gradlebuild/binarycompatibility/AlphabeticalAcceptedApiChangesTask.kt
import org.gradle.api.tasks.CacheableTask import org.gradle.api.tasks.TaskAction /** * This [Task][org.gradle.api.Task] checks that the contents of a given accepted API changes file * are present in alphabetical order (by type, then member), and throws an exception and reports * any changes that are not. */ @CacheableTask abstract class AlphabeticalAcceptedApiChangesTask : AbstractAcceptedApiChangesMaintenanceTask() {
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Sep 30 18:18:04 GMT 2022 - 2K bytes - Viewed (0) -
build-logic/binary-compatibility/src/test/kotlin/gradlebuild/binarycompatibility/AbstractAcceptedApiChangesMaintenanceTaskIntegrationTest.kt
run(":verifyAcceptedApiChangesOrdering") .forwardStdError(standardError) .buildAndFail() val expectedOutput = "API changes in file '${acceptedApiChangesFile.name}' should be in alphabetical order (by type and member), yet these changes were not:\n" val cleanupHint = "To automatically alphabetize these changes run: 'gradlew :architecture-test:sortAcceptedApiChanges'" with(standardError) {
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Nov 28 21:09:42 GMT 2022 - 5.6K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/kotlin/gradlebuild/binarycompatibility/SortAcceptedApiChangesTask.kt
import org.gradle.api.tasks.CacheableTask import org.gradle.api.tasks.TaskAction /** * This [Task][org.gradle.api.Task] reorders the changes in an accepted API changes file * so that they are alphabetically sorted (by type, then member). */ @CacheableTask abstract class SortAcceptedApiChangesTask : AbstractAcceptedApiChangesMaintenanceTask() { @TaskAction fun execute() {
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Sep 30 18:18:04 GMT 2022 - 2.1K bytes - Viewed (0) -
.github/CODEOWNERS
## ## CODEOWNERS style rules: ## 1. Prefer team ownership over individual user ownership. ## 2. GBT-related team should be listed first. ## 3. Try to keep paths alphabetically sorted within visual groups. ## 4. List individual owners last. ## # bt-unassigned-maintainers must be the first owner # All directories that are not explicitly listed below are considered
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 15:52:09 GMT 2024 - 9.8K bytes - Viewed (0)