- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 17 for variant_model (0.24 sec)
-
platforms/documentation/docs/src/docs/userguide/dep-man/04-modeling-features/variant_model.adoc
Tom Tresansky <******@****.***> 1712091018 -0400
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 02 20:50:18 UTC 2024 - 34.2K bytes - Viewed (0) -
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/internal/component/ResolutionFailureHandlerIntegrationTest.groovy
assertSuggestsReviewingAlgorithm() assertSuggestsViewingDocs("Ambiguity errors are explained in more detail at https://docs.gradle.org/${GradleVersion.current().version}/userguide/variant_model.html#sub:variant-ambiguity.")
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 28 15:55:38 UTC 2024 - 45K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/01-core-dependency-management/viewing_debugging_dependencies.adoc
[[sec:resolving-variant-aware-errors]] === Variant Selection Errors Sometimes a selection error happens at the <<variant_model.adoc#understanding-variant-selection,variant selection level>>. Have a look at the <<variant_model.adoc#sec:variant-select-errors,dedicated section>> to understand these errors and how to resolve them. [[sub:resolving-unsafe-configuration-resolution-errors]]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 28 15:55:38 UTC 2024 - 12K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/dependency_management_terminology.adoc
Examples of variants each Java components typically offers are _api_ and _runtime_ variants. Others examples are JDK8 and JDK11 variants. For more information, see the section on <<variant_model.adoc#understanding-variant-selection,variant selection>>. [[sub:terminology_attribute]] == Variant Attribute Attributes are used to identify and select <<#sub:terminology_variant,variants>>.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Dec 01 18:45:05 UTC 2023 - 11.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/03-controlling-transitive-dependencies/component_metadata_rules.adoc
The main difference between writing rules and defining dependencies and artifacts in the build script is that component metadata rules, following the structure of Gradle Module Metadata, operate on <<variant_model.adoc#understanding-variant-selection,variants>> directly.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue May 28 15:10:53 UTC 2024 - 33.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/04-modeling-features/artifact_transforms.adoc
Gradle identifies a variant of a dependency uniquely by its set of <<variant_model.adoc#sec:abm_configuration_attributes,attributes>>. The `java-api` variant of a dependency is the variant identified by the `org.gradle.usage` attribute with value `java-api`. When Gradle resolves a configuration, the <<variant_model.adoc#sec:abm_configuration_attributes,attributes>> on the resolved configuration determine the _requested attributes_.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 20.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/native/swift_testing.adoc
==== In this example, we use a convention plugin `myproject.xctest-conventions` to expose the test results from a project to Gradle's <<variant_model.adoc#understanding-variant-selection,variant aware dependency management engine>>. The plugin declares a consumable `binaryTestResultsElements` configuration that represents the binary test results of the `test` task.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 10.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/03-controlling-transitive-dependencies/resolution_rules.adoc
[[sec:variant_aware_substitutions]] === Substituting a dependency with another variant Gradle's dependency management engine is <<variant_model.adoc#understanding-variant-selection,variant-aware>> meaning that for a single component, the engine may select different artifacts and transitive dependencies.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Jan 17 00:09:06 UTC 2024 - 30.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/04-modeling-features/variant_attributes.adoc
// See the License for the specific language governing permissions and // limitations under the License. [[variant_attributes]] = Working with Variant Attributes As explained in the section on <<variant_model.adoc#sec:variant-aware-matching,variant aware matching>>, attributes give semantics to variants and are used by Gradle's dependency management engine to select the best matching variant.
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/04-modeling-features/cross_project_publications.adoc
However, the consumer has to explicitly tell which configuration it depends on, which is something we want to avoid in _variant aware resolution_. In fact, we also <<variant_model.adoc#understanding-variant-selection, have explained>> that it is possible for a consumer to express requirements using _attributes_ and that the producer should provide the appropriate outgoing variants using attributes too.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Dec 07 01:37:51 UTC 2023 - 18K bytes - Viewed (0)