- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for track (0.12 sec)
-
build-logic-commons/module-identity/src/main/kotlin/gradlebuild.module-jar.gradle.kts
} val to = dependency.resolvedVariant when (val fromComponent = dependency.from.id) { is ProjectComponentIdentifier -> if (fromComponent != rootComponent.id) { // Only track accessible dependencies from _transitive_ local dependencies // We should not include the root variant's dependencies in the locally accessible set locallyAccessible.add(to.owner) }
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Mar 28 20:26:58 GMT 2024 - 4.3K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
* Review in Google Docs is not as simple as a PR code review in GitHub ## Decision The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as the *build tool* team) want to promote.
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) -
build-logic/jvm/src/main/kotlin/gradlebuild.unittest-and-compile.gradle.kts
fun Test.addOsAsInputs() { // Add OS as inputs since tests on different OS may behave differently https://github.com/gradle/gradle-private/issues/2831 // the version currently differs between our dev infrastructure, so we only track the name and the architecture inputs.property("operatingSystem", "${OperatingSystem.current().name} ${System.getProperty("os.arch")}") }
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Wed Jan 17 13:36:27 GMT 2024 - 15.7K bytes - Viewed (0) -
architecture/build-state-model.md
# Build state model The Gradle daemon tracks state for various elements. These are arranged in a hierarchy: ```mermaid graph TD process["build process"] session["build session"] process --> session build_tree["build tree"] session --> build_tree build1["root build"] build_tree --> build1 project1["root project"] build1 --> project1 project2["project"] build1 --> project2
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) -
architecture/README.md
See [Gradle runtimes](runtimes.md) for a list of these runtimes and more details. ## Build state model As Gradle executes, it acts on various pieces of the build definition, such as each project in the build. Gradle tracks the state of each piece and transitions each piece through its lifecycle as the build runs.
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) -
build-logic/jvm/src/main/kotlin/gradlebuild.launchable-jar.gradle.kts
val startScripts = tasks.register<GradleStartScriptGenerator>("startScripts") { 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.
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)