- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 54 for content_es (0.1 sec)
-
.github/workflows/arm-ci.yml
Registered: Sun Jun 16 05:45:23 UTC 2024 - Last Modified: Wed Feb 07 17:41:21 UTC 2024 - 2.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/tasks/implementing_custom_tasks.adoc
|`@PathSensitive` |Property is one or more files and only the given part of the file path is important |`@IgnoreEmptyDirectories` |Used with `@InputFiles` or `@InputDirectory` to instruct Gradle to track only changes to the contents of directories and not differences in the directories themselves. |`@NormalizeLineEndings`
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Apr 26 05:34:54 UTC 2024 - 37.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/reference/command_line_interface.adoc
=== Running all checks It is common for _all_ verification tasks, including tests and linting, to be executed using the `check` task: ---- $ gradle check ---- === Cleaning outputs You can delete the contents of the build directory using the `clean` task. Doing so will cause pre-computed outputs to be lost, causing significant additional build time for the subsequent task execution: ---- $ gradle clean ----
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 05:36:09 UTC 2024 - 34.8K bytes - Viewed (0) -
.github/workflows/mint.yml
- master # This ensures that previous jobs for the PR are canceled when the PR is # updated. concurrency: group: ${{ github.workflow }}-${{ github.head_ref }} cancel-in-progress: true permissions: contents: read jobs: mint-test: runs-on: mint timeout-minutes: 120 steps: - name: cleanup #https://github.com/actions/checkout/issues/273 run: |
Registered: Sun Jun 16 00:44:34 UTC 2024 - Last Modified: Tue Jun 04 15:12:57 UTC 2024 - 2.9K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/migrating/migrating_from_maven.adoc
+ . Develop a mechanism to verify that the two builds produce the same artifacts. + This is a vitally important step to ensure that your deployments and tests don't break. Even small changes, such as the contents of a manifest file in a JAR, can cause problems.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Mar 23 22:37:03 UTC 2024 - 40.6K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/build-cache/build_cache_concepts.adoc
As input normalization is declared by the task _consuming_ the data as input, different tasks can define different ways to normalize the same data. When it comes to file inputs, Gradle can normalize the path of the files as well as their contents. [[relocatability]] === Path sensitivity and relocatability When sharing cached results between computers, it's rare that everyone runs the build from the exact same location on their computers.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Nov 29 17:38:38 UTC 2023 - 13.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/04-modeling-features/variant_attributes.adoc
| link:{javadocPath}/org/gradle/api/attributes/LibraryElements.html#LIBRARY_ELEMENTS_ATTRIBUTE[`org.gradle.libraryelements`] | Indicates the contents of a `org.gradle.category=library` variant | `LibraryElements` values built from constants defined in link:{javadocPath}/org/gradle/api/attributes/LibraryElements.html[LibraryElements]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Mar 26 18:51:23 UTC 2024 - 17.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/03-controlling-transitive-dependencies/resolution_strategy_tuning.adoc
This is possible in the following cases: - dynamic dependency versions are used (version ranges, `latest.release`, `1.+`, ...) - or _changing_ versions are used (SNAPSHOTs, fixed version with changing contents, ...) The recommended way to deal with dynamic versions is to use <<dependency_locking.adoc#dependency-locking,dependency locking>>.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 9.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/gradle-properties/working_with_files.adoc
It synchronizes the contents of a directory with its source. This can be useful for doing things such as installing your application, creating an exploded copy of your archives, or maintaining a copy of the project's dependencies.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Apr 24 04:19:09 UTC 2024 - 70.5K bytes - Viewed (0) -
src/runtime/sys_linux_386.s
// unsigned long base_addr; // unsigned int limit; // unsigned int seg_32bit:1; // unsigned int contents:2; // unsigned int read_exec_only:1; // unsigned int limit_in_pages:1; // unsigned int seg_not_present:1; // unsigned int useable:1; // }; #define SEG_32BIT 0x01 // contents are the 2 bits 0x02 and 0x04. #define CONTENTS_DATA 0x00 #define CONTENTS_STACK 0x02 #define CONTENTS_CODE 0x04
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Fri Mar 24 18:53:44 UTC 2023 - 17.9K bytes - Viewed (0)