Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 64 for does (0.14 sec)

  1. 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)
  2. build-logic-commons/basics/src/main/kotlin/gradlebuild/basics/BuildEnvironment.kt

        }
    }
    
    
    fun Project.releasedVersionsFile() = repoRoot().file("released-versions.json")
    
    
    /**
     * We use command line Git instead of JGit, because JGit's `Repository.resolve` does not work with worktrees.
     */
    fun Project.currentGitBranchViaFileSystemQuery(): Provider<String> = getBuildEnvironmentExtension()?.gitBranch ?: objects.property(String::class.java)
    
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Feb 09 22:52:01 GMT 2024
    - 5.7K bytes
    - Viewed (2)
  3. 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)
  4. build-logic/kotlin-dsl-shared-runtime/src/main/kotlin/org/gradle/kotlin/dsl/internal/sharedruntime/codegen/ApiTypeProvider.kt

     * Once closed, type graph navigation from [ApiType] and [ApiFunction] instances
     * will throw [IllegalStateException].
     *
     * Limitations:
     * - supports Java byte code only, not Kotlin
     * - does not support nested Java arrays as method parameters
     * - does not support generics with multiple bounds
     */
    class ApiTypeProvider internal constructor(
        private val asmLevel: Int,
        private val incubatingAnnotationTypeDescriptor: String,
    Plain Text
    - Registered: Wed Feb 28 11:36:09 GMT 2024
    - Last Modified: Tue Feb 06 19:56:10 GMT 2024
    - 20.8K bytes
    - Viewed (0)
  5. .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)
  6. architecture/standards/0002-avoid-using-java-serialization.md

    With Java serialization, even minor changes to a class (like adding a field) can break compatibility.
    
    - **Cross-Language Compatibility:**
    Java serialization is inherently Java-centric and does not support cross-language scenarios well.
    
    - **Type Safety:**
    Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors.
    
    ## Decision
    
    We do not use Java serialization.
    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)
  7. architecture/standards/0004-use-a-platform-architecture.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: Sun Feb 25 22:19:29 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  8. architecture/standards/0005-introduce-core-ui-architecture-module.md

    - The console and CLI, as a specific implementation of these services.
    
    The UI architecture module uses the core runtime architecture module. It provides APIs that are used by the other modules and platforms. 
    
    This ADR does not specify the owner of this new architecture module. However, as a separate module, it can be assigned ownership independently of the other core services.
    
    ## Status
    
    ACCEPTED
    
    ## Consequences
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Mon Mar 04 23:19:15 GMT 2024
    - 1.3K bytes
    - Viewed (0)
  9. .teamcity/src/main/kotlin/promotion/PublishBranchSnapshotFromQuickFeedback.kt

    ) {
        init {
            id("Promotion_PublishBranchSnapshotFromQuickFeedback")
            name = "Publish Branch Snapshot (from Quick Feedback)"
            description = "Deploys a new distribution snapshot for the selected build/branch. Does not update master or the documentation."
    
            val triggerName = this.triggerName
    
            params {
                param("branch.qualifier", "%dep.${RelativeId("Check_Stage_${triggerName}_Trigger")}.teamcity.build.branch%")
    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)
  10. build-logic/jvm/src/main/kotlin/gradlebuild.launchable-jar.gradle.kts

        startScriptsDir = layout.buildDirectory.dir("startScripts")
        launcherJar.from(tasks.jar)
        agentJars.from(agentsClasspath)
        // The trick below is to use the templates from the current code instead of the wrapper. It does not cover the case where the generation logic is updated though.
        unixScriptTemplate.from(layout.projectDirectory.file("../../../platforms/jvm/plugins-application/src/main/resources/org/gradle/api/internal/plugins/unixStartScript.txt"))
    Plain Text
    - Registered: Wed Mar 27 11:36:08 GMT 2024
    - Last Modified: Wed Feb 28 23:38:57 GMT 2024
    - 2.5K bytes
    - Viewed (0)
Back to top