- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 22 for Searle (0.09 sec)
-
platforms/documentation/docs/src/docs/userguide/api/kotlin_dsl.adoc
+ image::intellij-script-dependencies-reload.png[Reload script dependencies] We recommend that you _disable automatic build import_, but _enable automatic reloading of script dependencies_. That way you get early feedback while editing Gradle scripts and control over when the whole build setup gets synchronized with your IDE. === Troubleshooting The IDE support is provided by two components:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 22 20:16:10 UTC 2024 - 55.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_8.adoc
Previously, this logic would have omitted the two above noted attributes entirely, while now the same logic will copy the attributes and finalize the project's Java toolchain. To avoid early toolchain finalization, attribute-copying logic should be updated to query the source Configuration's attributes lazily: ===== [.multi-language-sample] ====== .build.gradle.kts [source,kotlin] ----
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Jun 07 17:01:07 UTC 2024 - 90.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/tutorial/partr6_writing_tasks.adoc
Actions are added to a Task via the `doFirst{}` and `doLast{}` closures. A Task can depend on other tasks. == Step 2. Register and Configure Tasks Early on in the tutorial, we registered and configured `task1` in the `app` build script: [.multi-language-sample] ===== .app/build.gradle.kts [source,kotlin] ---- tasks.register("task1"){ // <1>
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 17:16:27 UTC 2024 - 7.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/other/init_scripts.adoc
[[init_scripts]] = Initialization Scripts Initialization scripts are scripts that run before the build script is executed. They allow you to customize the build environment or configure settings early in the build. Initialization scripts can be useful for setting up common configurations, such as repositories, plugins, or custom tasks, across multiple projects. [[sec:basic_usage]] == Using an init script
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 05:36:09 UTC 2024 - 8.2K bytes - Viewed (0) -
src/runtime/race_arm64.s
// R9 = addr of target function TEXT racecallatomic<>(SB), NOSPLIT, $0 // Set up these registers // R0 = *ThreadState // R1 = caller pc // R2 = pc // R3 = addr of incoming arg list // Trigger SIGSEGV early. MOVD 40(RSP), R3 // 1st arg is addr. after two times BL, get it at 40(RSP) MOVB (R3), R13 // segv here if addr is bad // Check that addr is within [arenastart, arenaend) or within [racedatastart, racedataend).
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri May 17 18:37:29 UTC 2024 - 15.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/plugins/testing_gradle_plugins.adoc
Manual testing has its place in the development process, but it is not a replacement for automated testing. == Setting up automated tests Setting up a suite of tests early on is crucial to the success of your plugin. Automated tests become an invaluable safety net when upgrading the plugin to a new Gradle version or enhancing/refactoring the code. === Organizing test source code
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Mar 18 22:49:20 UTC 2024 - 16K bytes - Viewed (0) -
src/crypto/sha256/sha256block_amd64.s
MOVQ p_len+16(FP), numBytes // get number of input bytes to hash SHRQ $6, numBytes // force modulo 64 input buffer length SHLQ $6, numBytes CMPQ numBytes, $0 // exit early for zero-length input buffer JEQ done ADDQ dataPtr, numBytes // point numBytes to end of input buffer VMOVDQU (0*16)(digestPtr), state0 // load initial hash values and reorder
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Mar 04 17:29:44 UTC 2024 - 47.3K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/gradle-properties/working_with_files.adoc
// See the License for the specific language governing permissions and // limitations under the License. [[working_with_files]] = Working With Files File operations are fundamental to nearly every Gradle build. They involve handling source files, managing file dependencies, and generating reports. Gradle provides a robust API that simplifies these operations, enabling developers to perform necessary file tasks easily.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Apr 24 04:19:09 UTC 2024 - 70.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/configuration_cache.adoc
[[config_cache:stable]] == Stable configuration cache Working towards the stabilization of configuration caching we implemented some strictness behind a feature flag when it was considered too disruptive for early adopters. You can enable that feature flag as follows: ==== include::sample[dir="snippets/configurationCache/stableFeatureFlag/kotlin",files="settings.gradle.kts[]"]
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/authoring-builds/tasks/controlling_task_execution.adoc
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Mar 23 22:37:03 UTC 2024 - 14.2K bytes - Viewed (0)