- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 18 for content_es (0.13 sec)
-
platforms/documentation/docs/src/docs/userguide/optimizing-performance/build-cache/common_caching_problems.adoc
If the absolute path represents a tool being used it probably makes sense to track the tool version as an input instead. For example, if you are using tools in your `Test` task called `integTest` which depend on the contents of the `LANG` variable you should do this: ====
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 19.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/troubleshooting/validation_problems.adoc
If you use the `@Input` annotation on a file-based property, Gradle wouldn't consider the file contents, or the directory contents, as inputs, as you might expect.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Mar 23 22:37:03 UTC 2024 - 21.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/06-publishing/publishing_ivy.adoc
* Standard metadata like `module`, `organisation` and `revision`. * Other contents of the module descriptor — via link:{groovyDslPath}/org.gradle.api.publish.ivy.IvyPublication.html#org.gradle.api.publish.ivy.IvyPublication:descriptor(org.gradle.api.Action)[IvyPublication.descriptor(org.gradle.api.Action)].
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Feb 23 03:39:56 UTC 2024 - 13.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/02-declaring-dependency-versions/dynamic_versions.adoc
- new versions of dynamic dependencies - new versions of changing modules (modules which use the same version string but can have different contents) -- Refreshing dependencies will cause Gradle to invalidate its listing caches. However: - it will perform HTTP HEAD requests on metadata files but _will not re-download them_ if they are identical
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Nov 29 17:38:38 UTC 2023 - 13.6K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/installation.adoc
This is especially useful when multiple JDKs are installed: ---- ❯ echo %JAVA_HOME% C:\Program Files\Java\jdk1.7.0_80 ---- ---- ❯ echo $JAVA_HOME /Library/Java/JavaVirtualMachines/jdk-16.jdk/Contents/Home ---- Gradle supports link:https://kotlinlang.org/[Kotlin] and link:https://groovy-lang.org/[Groovy] as the main build languages.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Feb 05 18:33:11 UTC 2024 - 10.6K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/migrating/migrating_from_ant.adoc
2. 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 - 37.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/01-core-dependency-management/declaring_repositories.adoc
It's even more important when considering that the declared order of repositories matter. [[sec:declaring-repository-filter]] === Declaring a repository filter .Declaring repository contents ==== include::sample[dir="snippets//dependencyManagement/declaringRepositories-filtering/kotlin",files="build.gradle.kts[tags=repository-filter]"]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 43.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/toolchains.adoc
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Apr 26 05:37:54 UTC 2024 - 24.8K 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)