- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 62 for tooling (0.03 sec)
-
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/AbstractBuildScanInfoCollectingService.kt
import org.gradle.api.services.BuildService import org.gradle.api.services.BuildServiceParameters import org.gradle.tooling.events.FinishEvent import org.gradle.tooling.events.OperationCompletionListener import org.gradle.tooling.events.task.TaskFinishEvent import org.gradle.tooling.events.task.TaskOperationResult import java.io.Serializable /**
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Tue Jun 10 05:45:46 UTC 2025 - 2.3K bytes - Viewed (0) -
architecture/standards/0007-java-pre-requisite.md
* This starts the [Gradle Launcher](https://blog.gradle.org/how-gradle-works-1#local-gradle-distribution-in-cli), which itself requires a JVM * The [Gradle Tooling API client](https://docs.gradle.org/8.8/userguide/third_party_integration.html#embedding) * This requires a Java application, and thus runtime, to run the tooling API client As indicated, each of those components require a Java runtime to run.
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Tue Jan 07 08:44:20 UTC 2025 - 3.3K bytes - Viewed (0) -
build-logic/integration-testing/src/main/kotlin/gradlebuild/integrationtests/tasks/DistributionTest.kt
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Mon Aug 18 18:02:41 UTC 2025 - 7.7K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.collect-failed-tasks.gradle.kts
import gradlebuild.AbstractBuildScanInfoCollectingService import gradlebuild.registerBuildScanInfoCollectingService import io.gitlab.arturbosch.detekt.Detekt import org.gradle.tooling.events.task.TaskFailureResult import org.gradle.tooling.events.task.TaskOperationResult import java.io.Serializable import java.util.concurrent.CopyOnWriteArrayList /**
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Fri Apr 11 20:57:49 UTC 2025 - 2.4K bytes - Viewed (0) -
architecture/build-execution-model.md
4. The daemon runs the request, sending back data such as logging output or tooling API events and intermediate models while doing so. 5. The daemon sends the result back. For some requests, this might be a simple success/failure result, and for others this might also include a more complex object, such as a tooling API model.
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Thu Jun 12 09:50:57 UTC 2025 - 907 bytes - Viewed (0) -
architecture/runtimes.md
- CLI client. This is the `gradle` or `gradlew` command, and is responsible for locating, starting and interacting with the Gradle daemon, potentially downloading the Gradle distribution. - Tooling API client. This a library that is embedded into applications, such as IDEs or CI agents, that allows them to act as a Gradle client.
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Thu May 02 06:42:46 UTC 2024 - 2.3K bytes - Viewed (0) -
build-logic-commons/publishing/src/main/kotlin/gradlebuild.publish-public-libraries.gradle.kts
builtBy(localPublish) } } if (signArtifacts) { // Otherwise we get // ask ':tooling-api:publishGradleDistributionPublicationToRemoteRepository' uses this output of task ':tooling-api:signLocalPublication' // without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Thu Oct 30 16:56:31 UTC 2025 - 5.7K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.cache-miss-monitor.gradle.kts
import com.gradle.develocity.agent.gradle.scan.BuildScanConfiguration import gradlebuild.AbstractBuildScanInfoCollectingService import gradlebuild.registerBuildScanInfoCollectingService import org.gradle.tooling.events.task.TaskOperationResult import org.gradle.tooling.events.task.TaskSuccessResult import java.io.Serializable import java.util.concurrent.atomic.AtomicBoolean /**
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Fri Apr 11 20:57:49 UTC 2025 - 4.8K bytes - Viewed (0) -
build-logic/dependency-modules/src/main/kotlin/gradlebuild.dependency-modules.gradle.kts
) // TODO: Gradle profiler should use the bundled tooling API. // This should actually be handled by conflict resolution, though it doesn't seem to work. // See https://github.com/gradle/gradle/issues/12002. applyRule<DependencyRemovalByNameRule>( "org.gradle.profiler:gradle-profiler", setOf("gradle-tooling-api") ) } }Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Fri Jul 18 11:32:19 UTC 2025 - 9.3K bytes - Viewed (0) -
architecture/README.md
### Build execution model Gradle generally does some work in response to a client request. There are several different clients, for example the `gradlew` command or the tooling API client, that can send requests to a Gradle daemon. Each daemon runs one request at a time. Generally speaking, the daemons only act in response to a request from a client and do not take any action on their own.
Registered: Wed Dec 31 11:36:14 UTC 2025 - Last Modified: Thu Jun 12 09:50:57 UTC 2025 - 3.6K bytes - Viewed (0)