Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 9 of 9 for existent (0.24 sec)

  1. build-logic/binary-compatibility/src/test/kotlin/gradlebuild/binarycompatibility/KotlinInternalFilteringTest.kt

            checkBinaryCompatibleKotlin(
                v1 = existingSource,
                v2 = internalSource
            ).assertEmptyReport()
        }
    
        @Test
        fun `existing internal members made public appear as added`() {
    
            checkNotBinaryCompatibleKotlin(
                v1 = internalSource,
                v2 = publicSource
            ).apply {
                assertHasErrors(
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Jul 11 06:57:51 GMT 2023
    - 6.2K bytes
    - Viewed (0)
  2. .teamcity/src/main/kotlin/promotion/PublishBranchSnapshotFromQuickFeedback.kt

                    "%branch.qualifier%",
                    label = "Branch to promote",
                    description = "Type in the branch of gradle/gradle you want to promote. Leave the default value when promoting an existing build.",
                    display = ParameterDisplay.PROMPT,
                    allowEmpty = false
                )
            }
        }
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Tue Dec 05 00:08:14 GMT 2023
    - 1.9K bytes
    - Viewed (0)
  3. architecture/standards/0002-avoid-using-java-serialization.md

    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    * The configuration cache serialization infrastructure should be used for all serialization.
    * Existing usages of Serializer outside of this infrastructure should be migrated to use it.
    * Existing usages of Java serialization should be migrated to use it.
    * It is ok for Serializer to be used as a replacement for Java serialization as a migration step.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu Feb 29 22:32:18 GMT 2024
    - 2.3K bytes
    - Viewed (0)
  4. architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md

    ## Decision
    
    We do not introduce new public API methods that include Groovy types in their signatures.
    Existing Groovy methods will not be removed immediately.
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    * If we would have used `Closure`, we must instead use `Action<T>`, `Spec<T>`, `Callable<T>`, or `Transformer<OUT, IN>`.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sun Mar 10 20:38:06 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  5. CONTRIBUTING.md

    - Make sure  "Use default gradle wrapper" is selected
    - Select a Java 11 VM as "Gradle JVM"
    - In the "File already exists" dialogue, choose "Yes" to overwrite
    - In the "Open Project" dialogue, choose "Delete Existing Project and Import"
    - Revert the Git changes to files in the `.idea` folder
    
    NOTE: Due to the project size, the very first import can take a while and IntelliJ might become unresponsive for several seconds during this period.
    
    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)
  6. build-logic/integration-testing/src/main/kotlin/gradlebuild.cross-version-tests.gradle.kts

                // We should always be using JUnitPlatform at this point, so don't call useJUnitPlatform(), else this will
                // discard existing options configuration and add a deprecation warning.  Just set the existing options.
                (this.testFramework.options as JUnitPlatformOptions).includeEngines("cross-version-test-engine")
            }
            if (executer == defaultExecuter) {
    Plain Text
    - Registered: Wed Mar 27 11:36:08 GMT 2024
    - Last Modified: Sat Sep 30 16:17:28 GMT 2023
    - 4.1K bytes
    - Viewed (0)
  7. build-logic/binary-compatibility/src/test/kotlin/gradlebuild/binarycompatibility/SinceAndIncubatingRulesKotlinTest.kt

                )
            }
    
            // with existing non-incubating file-facade class, new members must be annotated with @Incubating and @since
            checkBinaryCompatibleKotlin(
                v1 = """
                    val existing = "file-facade-class"
                """,
                v2 = """
                    val existing = "file-facade-class"
    
                    $annotatedKotlinMembers
    
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Jul 11 06:57:51 GMT 2023
    - 12.7K bytes
    - Viewed (0)
  8. .teamcity/src/main/kotlin/configurations/FlakyTestQuarantine.kt

        if (os == Os.LINUX) {
            steps {
                script {
                    // Because we exclude tests in `distributions-integ-tests` below, `@Flaky` won't work in that subproject.
                    // Here we check the existence of `@Flaky` annotation to make sure nobody use that annotation in `distributions-integ-tests` subproject.
                    name = "MAKE_SURE_NO_@FLAKY_IN_DISTRIBUTIONS_INTEG_TESTS"
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 08:17:56 GMT 2024
    - 3.4K bytes
    - Viewed (0)
  9. build-logic/binary-compatibility/src/main/groovy/gradlebuild.binary-compatibility.gradle

        )
    }
    tasks.named("check").configure { dependsOn(checkBinaryCompatibility) }
    
    tasks.register("cleanAcceptedApiChanges", CleanAcceptedApiChanges) {
        description = 'Cleans up all existing accepted API changes.'
        jsonFile = apiChangesJsonFile.asFile
    }
    
    static List<String> toPatterns(List<String> packages) {
        packages.collect {
            it.replaceAll('\\*\\*', '###')
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Thu Apr 11 12:20:44 GMT 2024
    - 8.6K bytes
    - Viewed (0)
Back to top