- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 2,950 for Builds (0.13 sec)
-
platforms/ide/tooling-api/src/crossVersionTest/groovy/org/gradle/plugins/ide/tooling/r33/BuildActionCompositeBuildCrossVersionSpec.groovy
} singleProjectBuildInSubfolder("includedBuild") when: def builds = withConnection { action(new FetchBuilds()).run() } then: builds.rootProject.name == ["root", "includedBuild"] } def "Can fetch project scoped models from included builds"() { given: multiProjectBuildInRootFolder("root", ["a", "b"]) {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 16 10:10:39 UTC 2024 - 5.5K bytes - Viewed (0) -
platforms/software/platform-base/src/main/java/org/gradle/api/plugins/BasePluginExtension.java
/** * This method is only here to maintain compatibility with existing builds. * * @deprecated Use {@link #getDistsDirectory()}. This method is scheduled for removal in Gradle 9.0. */ @Deprecated String getDistsDirName(); /** * This method is only here to maintain compatibility with existing builds. *
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Oct 11 12:16:09 UTC 2023 - 2.9K bytes - Viewed (0) -
platforms/ide/tooling-api/src/crossVersionTest/groovy/org/gradle/integtests/tooling/r33/GradleBuildModelCrossVersionSpec.groovy
import org.gradle.tooling.model.gradle.GradleBuild import spock.lang.Issue class GradleBuildModelCrossVersionSpec extends ToolingApiSpecification { @TargetGradleVersion(">=3.3") def "Included builds are present in the model"() { given: def rootDir = singleProjectBuildInRootFolder("root") { settingsFile << """ rootProject.name = 'root'
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 16 10:10:39 UTC 2024 - 3.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/overview/about_manual.adoc
<<getting_started_eng.adoc#introduction,Running Gradle Builds>> :: Learn Gradle basics and how to use Gradle to build your project. <<build_lifecycle.adoc#build_lifecycle,Authoring Gradle Builds>> :: Develop tasks and plugins to customize your build. <<building_java_projects.adoc#building_java_projects,Authoring JVM Builds>> :: Use Gradle with your Java project.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 02 07:52:44 UTC 2024 - 2K bytes - Viewed (0) -
platforms/documentation/docs/src/samples/build-organization/composite-builds/hierarchical-multirepo/README.adoc
== Using composite builds in a hierarchical multirepo project This sample demonstrates how composite builds can be used to develop a hierarchical project that is composed from different Git repositories. Instead of Gradle subprojects in a multiproject build, this example uses separate Gradle builds included into a composite.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 3.9K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/tutorial/partr3_multi_project_builds.adoc
Composite builds allow you to: - Extract your build logic from your project build (and re-use it among subprojects) - Combine builds that are usually developed independently (such as a plugin and an application) - Decompose a large build into smaller, more isolated chunks == Step 4. Add build to the Build Let's add a plugin to our build. First, create a new directory called `license-plugin` in the `gradle` directory:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 17:16:27 UTC 2024 - 13.9K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/build-cache/build_cache_performance.adoc
1. Clean the cache directory to avoid any hits from previous builds (`rm -rf $GRADLE_USER_HOME/caches/build-cache-*`) 2. Run the build (e.g. `./gradlew --build-cache clean assemble`), so that all the results from cacheable tasks get stored in the cache. 3. Run the build again (e.g. `./gradlew --build-cache clean assemble`); depending on your build, you should see many of the tasks being retrieved from the cache.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 14 09:28:20 UTC 2024 - 9.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/running-builds/introduction/gradle_optimizations.adoc
Gradle uses two main features to reduce build time: *incremental builds* and *build caching*. image::gradle-basic-8.png[] == Incremental builds An *incremental build* is a build that avoids running tasks whose inputs have not changed since the previous build. Re-executing such tasks is unnecessary if they would only re-produce the same output. For incremental builds to work, tasks must define their inputs and outputs.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 14 09:28:20 UTC 2024 - 4.8K bytes - Viewed (0) -
platforms/ide/ide-plugins/src/test/groovy/org/gradle/plugins/ide/idea/model/internal/ModuleDependencyBuilderTest.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Aug 01 11:07:39 UTC 2023 - 2.1K bytes - Viewed (0) -
platforms/ide/tooling-api/src/main/java/org/gradle/tooling/TestLauncher.java
/** * * <p>A {@code TestLauncher} allows you to execute tests in a Gradle build.</p> * * <p>If the target Gradle version is >=6.8 then you can use {@code TestLauncher} to execute tests from included builds. Test operation descriptors from included builds work out-of-the-box. You can * target tasks from included builds by specifying the task identity path (i.e. {@code ':included-build-name:subproject-name:taskName'}).</p> *
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Sep 26 14:49:20 UTC 2023 - 8.6K bytes - Viewed (0)