Search Options

Results per page
Sort
Preferred Languages
Advance

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

  1. architecture/README.md

    For example, each process has different supported JVMs and a different set of services available for dependency injection.
    While a lot of Gradle source code runs only in the Gradle daemon, not all of it does and so, when working on some source code it is important to be aware of the runtimes in which it will run.
    
    See [Gradle runtimes](runtimes.md) for a list of these runtimes and more details.
    
    ## Build state model
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 06:42:46 GMT 2024
    - 2.4K bytes
    - Viewed (0)
  2. .teamcity/src/main/kotlin/configurations/GradleBuildConfigurationDefaults.kt

        if [ -e ${'$'}REPO ] ; then
            tree ${'$'}REPO
            rm -rf ${'$'}REPO
            echo "${'$'}REPO was polluted during the build"
            ${if (exitOnFailure) "exit 1" else ""}
        else
            echo "${'$'}REPO does not exist"
        fi
    
    """.trimIndent()
    
    fun checkCleanDirWindows(dir: String, exitOnFailure: Boolean = true) = """
        IF exist $dir (
            TREE $dir
            RMDIR /S /Q $dir
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Apr 24 08:17:56 GMT 2024
    - 7.9K bytes
    - Viewed (0)
  3. CONTRIBUTING.md

    Tasks known to have problems are listed in the build logic. You can find this list at:
    
        build-logic/root-build/src/main/kotlin/gradlebuild.internal.cc-experiment.gradle.kts
    
    If you discover a task that doesn't work with the configuration but it not in this list, please add it.
    
    For more information on the configuration cache, see the [user manual](https://docs.gradle.org/current/userguide/configuration_cache.html).
    
    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)
  4. architecture/build-state-model.md

    The build process state also includes state that is tied to a particular Gradle user home directory.
    When that directory changes between Gradle invocations, the state is discarded and recreated.
    Typically, the Gradle user home directory does not change for a given process, so this is effectively process state.
    
    The build process state is managed by the `BuildProcessState` class. An instance is created once for a given process.
    
    ### Build session state
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Sun May 05 22:45:11 GMT 2024
    - 3.4K bytes
    - Viewed (0)
  5. architecture/platforms.md

    This platform is agnostic to what exactly the purpose of the work is.
    It might be creating an application, setting up development environments, orchestrating deployments, running simulations, etc.
    
    This platform does not provide special support for a particular kind of automation. This is the responsibility of other platforms.
    
    It is made up of 3 architecture modules:
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Thu May 02 06:42:46 GMT 2024
    - 5.4K bytes
    - Viewed (0)
  6. build-logic/binary-compatibility/src/test/kotlin/gradlebuild/binarycompatibility/UpgradedPropertiesChangesTest.kt

                )
            }
        }
    
        @Test
        fun `should report an error if newly added method does not have @since`() {
            checkNotBinaryCompatible(
                v1 = {
                    withFile(
                        "java/com/example/Task.java",
                        """
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Tue Apr 23 08:40:36 GMT 2024
    - 20.2K bytes
    - Viewed (0)
Back to top