- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for Brunner (0.1 sec)
-
.github/workflows/codeql-analysis.yml
with: path: | ~/.gradle/caches/modules-2/ ~/.gradle/caches/build-cache-1/ ~/.gradle/caches/signatures/ ~/.gradle/caches/keyrings/ key: ${{ runner.os }}-gradle-cache-${{ hashFiles('gradle/wrapper/gradle-wrapper.properties') }} if: ${{ matrix.language == 'java' }} - name: Disable checksum offloading
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 02 09:13:16 UTC 2024 - 4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/other/test_kit.adoc
After creating and configuring a runner instance, the build can be executed via the link:{javadocPath}/org/gradle/testkit/runner/GradleRunner.html#build--[GradleRunner.build()] or link:{javadocPath}/org/gradle/testkit/runner/GradleRunner.html#buildAndFail--[GradleRunner.buildAndFail()] methods depending on the anticipated outcome. The following demonstrates the usage of the Gradle runner in a Java JUnit test:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 05:36:09 UTC 2024 - 15.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/plugins/testing_gradle_plugins.adoc
Some IDEs provide a convenience option to delegate the "test classpath generation and execution" to the build. In IntelliJ, you can find this option under Preferences... > Build, Execution, Deployment > Build Tools > Gradle > Runner > Delegate IDE build/run actions to Gradle.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Mar 18 22:49:20 UTC 2024 - 16K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/configuration_cache.adoc
For general guidance on how to use TestKit, see the <<test_kit.adoc#test_kit,dedicated chapter>>. To enable configuration caching in your tests, you can pass the `--configuration-cache` argument to link:{javadocPath}/org/gradle/testkit/runner/GradleRunner.html[GradleRunner] or use one of the other methods described in <<configuration_cache.adoc#config_cache:usage:enable,Enabling the configuration cache>>. You need to run your tasks twice.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 16:24:12 UTC 2024 - 71.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/core-plugins/build_init_plugin.adoc
* Generates dependencies (both external and inter-module) * Generates download repositories (inc. local Maven repository) * Adjusts Java compiler settings * Supports packaging of sources, tests, and javadocs * Supports TestNG runner * Generates global exclusions from Maven enforcer plugin settings * Provides <<build_init_plugin.adoc#sec:allow_insecure,an option for handling Maven repositories located at URLs using `http`>> [[sec:allow_insecure]]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed May 08 20:10:43 UTC 2024 - 19.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/java_testing.adoc
==== If you are using Eclipse: By default, Eclipse also runs unit tests as modules using module patching (see <<#sec:java_testing_modular_patching,below>>). In an imported Gradle project, unit testing a module with the Eclipse test runner might fail. You then need to manually adjust the classpath/module path in the test run configuration or delegate test execution to Gradle. This only concerns the test execution.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 16:24:12 UTC 2024 - 53.1K bytes - Viewed (0)