- Sort Score
- Result 10 results
- Languages All
Results 101 - 104 of 104 for content_es (0.12 sec)
-
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) -
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/resolve/transform/ArtifactTransformCachingIntegrationTest.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Jun 07 11:52:44 UTC 2024 - 97.8K 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)