- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for buildEnvironment (0.28 sec)
-
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_4.adoc
The full list of built-in tasks that should not be replaced is: `wrapper`, `init`, `help`, `tasks`, `projects`, `buildEnvironment`, `components`, `dependencies`, `dependencyInsight`, `dependentComponents`, `model`, `properties`. [[changes_4.7]] == Upgrading from 4.6 and earlier === Potential breaking changes
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Feb 22 03:01:48 UTC 2024 - 60.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/api/kotlin_dsl.adoc
w: build.gradle.kts:4:5: 'getter for uploadTaskName: String!' is deprecated. Deprecated in Java ---- It is possible to configure your build to fail on any warning emitted during script compilation by <<build_environment#sec:gradle_configuration_properties,setting>> the `org.gradle.kotlin.dsl.allWarningsAsErrors` Gradle property to `true`: [source,properties] ---- # gradle.properties org.gradle.kotlin.dsl.allWarningsAsErrors=true
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_7.adoc
* settings file in the root of the build * build file in the root of each subproject For the use case where custom settings or build files are used to model different behavior (similar to Maven profiles), consider using <<build_environment#sec:gradle_system_properties, system properties>> with conditional logic. For example, given a piece of code in either settings or build file: ``` if (System.getProperty("profile") == "custom") {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 87.7K bytes - Viewed (0)