- Sort Score
- Result 10 results
- Languages All
Results 71 - 79 of 79 for content_es (0.09 sec)
-
platforms/core-configuration/kotlin-dsl-provider-plugins/src/main/kotlin/org/gradle/kotlin/dsl/provider/plugins/precompiled/tasks/GeneratePrecompiledScriptPluginAccessors.kt
* hash code. * 5. For each group, for each script plugin in the group, write the generated package name to a file named * after the contents of the script plugin file. This is so the file can be easily found by * [PrecompiledScriptDependenciesResolver]. */ @TaskAction fun generate() { recreateTaskDirectories()
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Apr 18 08:10:49 UTC 2024 - 24.8K bytes - Viewed (0) -
platforms/jvm/plugins-application/src/integTest/groovy/org/gradle/api/plugins/ApplicationPluginIntegrationTest.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sun May 12 10:33:12 UTC 2024 - 23.6K bytes - Viewed (0) -
gradle/wrapper/gradle-wrapper.jar
distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that...
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Jan 26 08:44:14 UTC 2024 - 42.4K 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) -
subprojects/core-api/src/main/java/org/gradle/api/Task.java
/** * <p>Returns a directory which this task can use to write temporary files to. Each task instance is provided with a * separate temporary directory. There are no guarantees that the contents of this directory will be kept beyond the * execution of the task.</p> * * @return The directory. Never returns null. The directory will already exist. */ @Internal
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 30 17:25:12 UTC 2024 - 31.6K 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) -
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)